a year ago
[stage-0 6/10] RUN --mount=type=cache,id=s/c2e4ba0d-24fa-4469-bbcc-b1ef6cc7d882-/root/npm,target=/root/.npm npm ci
"npm ci" did not complete successfully: exit code: 1
npm warn config production Use --omit=dev instead.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/swagger@11.0.2
npm error Found: @nestjs/common@10.4.15
npm error node_modules/@nestjs/common
npm error @nestjs/common@"^10.0.0" from the root project
npm error peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/config@3.3.0
npm error node_modules/@nestjs/config
npm error @nestjs/config@"^3.3.0" from the root project
npm error 7 more (@nestjs/core, @nestjs/jwt, @nestjs/mapped-types, ...)
npm error
npm error Could not resolve dependency:
npm error peer @nestjs/common@"^11.0.1" from @nestjs/swagger@11.0.2
npm error node_modules/@nestjs/swagger
npm error @nestjs/swagger@"^11.0.2" from the root project
npm error
npm error Conflicting peer dependency: @nestjs/common@11.0.5
npm error node_modules/@nestjs/common
npm error peer @nestjs/common@"^11.0.1" from @nestjs/swagger@11.0.2
npm error node_modules/@nestjs/swagger
npm error @nestjs/swagger@"^11.0.2" from the root project
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.
npm error
npm error
npm error For a full report see:
npm error /root/.npm/_logs/2025-01-25T14_53_10_048Z-eresolve-report.txt
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-01-25T14_53_10_048Z-debug-0.log
ⓘ Deployment information is only viewable by project members and Railway employees.
0 Replies