npm upgrade
Home@prisma/config 6 → 7
6.19.3 → 7.10.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@prisma/config 7.10.0 removes or renames exports your code may import.
- Removed
- 1
- Renamed
- 0
- Signature changes
- 3
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 2
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @prisma/config@6.19.3..7.10.0
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- loadConfigFromPackageJsonfunction
Signature changes
Still exported, but the number of arguments it reads changed.
- defineConfig1 → 0 arguments
- env1 → 0 arguments
- loadConfigFromFile1 → 0 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 10, 2026. @prisma/config on lurq.