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

Abierto
#112 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
mongodb, node.js, typescript
Área
cli, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
12
Forks
0
Merge medio
43 min
PR fusionados (30 d)
8

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de prisma/create-prisma

Todos los issues de prisma/create-prisma

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.