MongoDB template fails under npm: ERESOLVE between mongodb@^7 (@prisma/orm-mongo) and alchemy's peerOptional mongodb@^6.10

Aperta
#112 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
mongodb, node.js, typescript
Ambito
cli, tooling

Direzione di ricerca

Start by reproducing the documented npm create command and compare it with the successful pnpm run. Inspect the MongoDB template's dependency generation and install path, especially how alchemy and mongodb versions are selected. Done means npm installs the template successfully without ERESOLVE and without leaving a partial project; add a regression check if the existing test structure supports one.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Summary

npm create prisma@latest -- <name> --template nest --provider mongodb fails during dependency installation with an ERESOLVE peer-dependency conflict. The generated package.json requires mongodb@^7.1.0 (and @prisma/[email protected] declares peer mongodb@^7.0.0), while [email protected], pulled in by @prisma/[email protected] and @prisma/[email protected], declares peerOptional mongodb@^6.10.0. npm refuses the resolution and leaves a half-generated project behind.

The same command with --package-manager pnpm succeeds, so the templates themselves are fine; the problem is npm's strict peer resolution against alchemy's peer range.

Reproduction

node -v   # v24.11.1
npm -v    # 11.6.2
npm create [email protected] -- nest-mongo --template nest --provider mongodb --yes --no-deploy

Output (trimmed):

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/mongodb
npm error   mongodb@"^7.1.0" from the root project
npm error   peer mongodb@"^7.0.0" from @prisma/[email protected]
npm error   node_modules/@prisma/orm-mongo
npm error     @prisma/orm-mongo@"8.0.0-rc.11" from the root project
npm error   2 more (@prisma/orm-family-mongo, @prisma/orm-target-mongo)
npm error
npm error Could not resolve dependency:
npm error peerOptional mongodb@"^6.10.0" from [email protected]
npm error node_modules/alchemy
npm error   alchemy@"2.0.0-beta.74" from the root project
npm error   alchemy@"2.0.0-beta.74" from @prisma/[email protected]
npm error   node_modules/@prisma/composer
npm error     @prisma/composer@"0.20.0" from the root project
npm error     1 more (@prisma/composer-prisma-cloud)
npm error
npm error Conflicting peer dependency: [email protected]
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

After the failure the target directory contains only package.json, tsconfig.json, and six src/*.ts files: no src/prisma/, no node_modules, no module.ts/service.ts.

Reproduced twice on 2026-09-24 (once with [email protected] from the npx cache, once with 0.13.2). The PostgreSQL template with the same flags installs cleanly under npm, and the MongoDB template installs cleanly with --package-manager pnpm:

npm create [email protected] -- nest-mongo --template nest --provider mongodb --package-manager pnpm --yes --no-deploy
# Prisma 8 project ready.

Relevant versions in the generated project

"@prisma/composer": "0.20.0",
"@prisma/composer-prisma-cloud": "0.20.0",
"@prisma/orm-mongo": "8.0.0-rc.11",
"alchemy": "2.0.0-beta.74",
"mongodb": "^7.1.0"

[email protected] (current latest) still declares peerDependencies.mongodb: "^6.10.0", so bumping the pinned alchemy version alone does not resolve it.

Expected behavior

The MongoDB template installs under npm, which is the package manager the docs lead with (npm create prisma@latest -- my-app).

Possible fixes

  • Add an npm overrides entry for mongodb (or run the npm install step with --legacy-peer-deps) in the MongoDB template until alchemy widens its peer range.
  • Ask upstream alchemy to declare peerOptional mongodb@"^6.10.0 || ^7.0.0", since the peer is optional and Composer does not use the MongoDB provider from alchemy here.
  • At minimum, fail before writing files, or print the pnpm workaround, so users are not left with a half-generated directory.

Context

Hit while verifying the "Prisma ORM 8 in NestJS" blog post; the post currently pins --package-manager pnpm for the MongoDB command as a workaround.

Lingua principale
TypeScript
Stelle
12
Fork
0
Merge medio
43m
PR unite (30g)
8

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di prisma/create-prisma

Tutte le issue di prisma/create-prisma

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.