@prisma/config

7.10.1 · 15 Oct 2026Apache-2.021.6M / weekRepository npm Atom feed

Upgrading @prisma/config From 6.17.0 to 6.19.3

Same major only

6 releases in betweenevery note read

Other targets from 6.17.0Latest7.10.1

6.19.3
Security fix1 Apr 2026
- security
  It updates the effect dependency to resolve a security vulnerability.
6.19.1 – 6.19.22 releases, nothing new or fixed in the notes
6.19.0
5 Nov 20256 new
- new
  When dropping a model from a schema, do not append the default schema to the migration.
- new
  Align naming conventions for fields and relation fields
- new
  Add biome ignore comments to generated client files. This was a community contribution from @lonelyevil, thank you!
- new
  Unified Prisma Config for project configuration
- new
  Move from prisma-client-js prisma-client
- new
  New engine and datasource keys in prisma.config.ts
6.18.0
22 Oct 20251 new
- new
  Support for defining your datasource in prisma.config.ts
6.17.1 nothing new or fixed in the note

8 other lines we could not sort, mostly version bumps

prisma init now creates a prisma.config.ts automatically
6.18.0
#28291 Support multiple Prisma instances with different providers
6.18.0
#28305 Add env helper function
6.18.0
#28266 Add support for js or classic as engine types in prisma.config
6.18.0
#28139 Map Bytes to Uint8Array depending on Typescript version
6.18.0
Total egress
6.18.0
Average response size
6.18.0
Average query duration
6.18.0

3 internal lines (docs, tests, tooling) left out.

npm install @prisma/config@6.19.3

Reading 6.19.3's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 6.19.3. Read once, not stored.