Not able to run npm ci

fcomir-ioHOBBY

a year ago

1.813 npm ERR! Fix the upstream dependency conflict, or retry
1.813 npm ERR! this command with --force or --legacy-peer-deps
1.813 npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

IHow can I make railway.app use flag --legacy-peer-deps in npm ci

View Deploy details

ⓘ Deployment information is only viewable by Project members and Railway admins.

5 Replies

a year ago

Do you not have any interest in property fixing the dependency conflicts?


fcomir-ioHOBBY

a year ago

Indeed I do, but don't know how or where to start
For sure solving the conflicts would be the right move
Any tips on this?
Thanks in advance Brody


fcomir-ioHOBBY

a year ago

While resolving: @nestjs/passport@9.0.3
Found: @nestjs/common@10.3.7
nodemodules/@nestjs/common peer @nestjs/common@"^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/axios@3.0.2 nodemodules/@nestjs/axios
peerOptional @nestjs/axios@"^1.0.0 || ^2.0.0 || ^3.0.0" from @nestjs/terminus@10.2.3
nodemodules/@nestjs/terminus @nestjs/terminus@"^10.2.3" from the root project @nestjs/axios@"^3.0.2" from the root project peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/config@3.2.2 nodemodules/@nestjs/config
@nestjs/config@"^3.2.2" from the root project
9 more (@nestjs/core, @nestjs/mapped-types, …)

Could not resolve dependency:
peer @nestjs/common@"^8.0.0 || ^9.0.0" from @nestjs/passport@9.0.3
node_modules/@nestjs/passport
@nestjs/passport@"^9.0.3" from the root project

Conflicting peer dependency: @nestjs/common@9.4.3
nodemodules/@nestjs/common peer @nestjs/common@"^8.0.0 || ^9.0.0" from @nestjs/passport@9.0.3 nodemodules/@nestjs/passport
@nestjs/passport@"^9.0.3" from the root project

This is what I get


a year ago

There are many resources that talk about resolving dependency conflicts out there.


fcomir-ioHOBBY

a year ago

Indeed there are a lot
Working on it
Thanks Brody