prisma.config.ts is a Prisma CLI config file, not part of the Next.js
app — exclude it from tsconfig to prevent type errors. Also revert the
migrate.adapter block (not a valid PrismaConfig key in 7.5) back to
datasource.url which is the correct CLI config for db push.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@libsql/client and libsql contain native bindings and non-JS assets
(README.md, LICENSE) that webpack cannot parse. Mark them as server
external packages so Next.js requires them at runtime instead.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Prisma 7 removed support for `url` in schema.prisma datasources and the
`engineType = "library"` native binary engine. All connections now go
through a driver adapter.
- Remove engineType and url from schema.prisma (no longer supported)
- Configure prisma.config.ts with migrate.adapter using @libsql/client
- Instantiate PrismaClient with PrismaLibSQL adapter in src/lib/prisma.ts
- Add @libsql/client and @prisma/adapter-libsql dependencies
- Remove PRISMA_CLIENT_ENGINE_TYPE from Dockerfile (obsolete)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Prisma 7's prisma.config.ts only configures the CLI, not the runtime
PrismaClient. Without url in the datasource block, the generated client
defaults to engineType "client" (WASM) which requires an adapter,
causing next-auth adapter errors on OAuth callback.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
