npm / @prisma/internals
@prisma/internals
What changed in @prisma/internals 6 to 7, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-20.
45 breaking5 deprecations3 new APIs and options3 behavior and defaults
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@prisma/internals 745 changes
Breaking changes 36
Prisma ORM no longer loads environment variables by default; explicitly load them when calling the Prisma CLI.
The generator output field is required, and Prisma Client is no longer generated in node_modules by default.
Prisma ORM v7 does not yet support MongoDB; MongoDB projects should continue using Prisma ORM v6 for now.
Prisma ORM v7 requires Node 20.19.0 or later; Node 22.x is recommended.
Prisma ORM now ships as an ES module, so set the package type to module.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
The --schema flag has been removed; configure the database connection in prisma.config.ts instead.
The --url flag has been removed; configure the database connection in prisma.config.ts instead.
db push no longer runs prisma generate automatically; run prisma generate explicitly to generate Prisma Client.
The --skip-generate flag has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
Running migrate dev no longer automatically executes the seed script or runs prisma generate; seed and generation must be run explicitly.
The --skip-generate flag has been removed.
The --skip-seed flag has been removed.
The --from-schema-datasource option has been removed and replaced by --from-config-datasource.
The --from-url option has been removed and replaced by --from-config-datasource.
The --shadow-database-url option has been removed; configure the shadow database URL in prisma.config.ts.
The --to-schema-datasource option has been removed and replaced by --to-config-datasource.
The --to-url option has been removed and replaced by --to-config-datasource.
Running migrate reset no longer automatically executes the seed script.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
This Prisma-specific environment variable has been removed.
The client middleware API has been removed; use Client Extensions where possible.
Generated client imports must use the configured output path instead of importing PrismaClient from @prisma/client.
Creating a Prisma Client now requires a driver adapter for all databases.
Invalid SSL certificates are no longer ignored by default; configure certificates or set rejectUnauthorized to false to keep the previous behavior.
TypeScript projects must configure their compiler to consume ES modules; the guide shows moduleResolution set to bundler.
Prisma ORM v7 requires TypeScript 5.4.0 or later; TypeScript 5.9.x is recommended.
Deprecations 5
The datasource directUrl field is deprecated; configure its value in prisma.config.ts, including for migrations.
The datasource shadowDatabaseUrl field is deprecated; configure it in Prisma Config.
The datasource url field is deprecated; configure the database URL in Prisma Config.
Standalone Prisma Accelerate and hosted Prisma Postgres Accelerate connections are scheduled for retirement; users should transition to pooled TCP or the Prisma Postgres serverless driver, or remove Accelerate.
Use the new Rust-free client generator provider; prisma-client-js is slated for removal in a future release.
New APIs and options 3
Use --from-config-datasource to use the datasource configured in Prisma Config as the source.
Use --to-config-datasource to use the datasource configured in Prisma Config as the target.
Prisma Config is now the default place to configure CLI database access, schema location, migration output, and seed scripts.
Behavior and default changes 1
Driver adapters use the underlying Node.js database driver's pool settings, which can differ from Prisma ORM v6 defaults and may require configuration to avoid timeouts.
@prisma/internals 611 changes
Breaking changes 9
async can no longer be used as a model name.
await can no longer be used as a model name.
Prisma v6 represents Bytes fields as Uint8Array instead of Buffer; update code that relies on Buffer types.
PostgreSQL users of full-text search must use the new Preview feature flag instead of fullTextSearch.
On PostgreSQL, Prisma changes the implicit relation table's unique index on A and B to a primary key, so the next migration will include ALTER TABLE statements for these relation tables.
Prisma ORM v6 requires Node.js 18.18.0, 20.9.0, or 22.11.0 at minimum and does not officially support Node.js 16, 17, 19, or 21.
NotFoundError is removed; handle PrismaClientKnownRequestError with code P2025 for findUniqueOrThrow() and findFirstOrThrow().
Prisma ORM v6 raises the minimum supported TypeScript version to 5.1.0.
using can no longer be used as a model name.
Behavior and default changes 2
The fullTextIndex feature is promoted to General Availability, so remove it from previewFeatures in the Prisma schema.
For MySQL, fullTextSearch is promoted to General Availability, so remove it from previewFeatures in the Prisma schema.