framework
kennierfranco
HOBBYOP

2 years ago

When I try to deploy my application, a dependency resolution error is generated. When I compile and run the application from a local environment, using the terminal, this problem does not occur. I have already deleted some dependencies that were causing conflict but the error keeps coming up again and again with a new dependency.


#11 7.186 npm ERR! ERESOLVE could not resolve

#11 7.186 npm ERR!

#11 7.186 npm ERR! While resolving: eslint-plugin-unused-imports@1.1.5

#11 7.186 npm ERR! Found: @typescript-eslint/eslint-plugin@5.62.0

#11 7.186 npm ERR! node_modules/@typescript-eslint/eslint-plugin

#11 7.186 npm ERR!   dev @typescript-eslint/eslint-plugin@"^5.56.0" from the root project

#11 7.186 npm ERR!

 

#11 7.186 npm ERR! Could not resolve dependency:

#11 7.186 npm ERR! peerOptional @typescript-eslint/eslint-plugin@"^4.14.2" from eslint-plugin-unused-imports@1.1.5

#11 7.186 npm ERR! node_modules/eslint-plugin-unused-imports

#11 7.187 npm ERR!   dev eslint-plugin-unused-imports@"^1.1.5" from the root project

#11 7.187 npm ERR!

#11 7.187 npm ERR! Conflicting peer dependency: @typescript-eslint/eslint-plugin@4.33.0

#11 7.187 npm ERR! node_modules/@typescript-eslint/eslint-plugin

#11 7.187 npm ERR!   peerOptional @typescript-eslint/eslint-plugin@"^4.14.2" from eslint-plugin-unused-imports@1.1.5

#11 7.187 npm ERR!   node_modules/eslint-plugin-unused-imports

#11 7.187 npm ERR!     dev eslint-plugin-unused-imports@"^1.1.5" from the root project

#11 7.187 npm ERR!

#11 7.187 npm ERR! Fix the upstream dependency conflict, or retry

#11 7.187 npm ERR! this command with --force, or --legacy-peer-deps

#11 7.187 npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

#11 7.187 npm ERR!

#11 7.187 npm ERR! See /root/.npm/eresolve-report.txt for a full report.

#11 7.189

#11 7.189 npm ERR! A complete log of this run can be found in:

#11 7.189 npm ERR!     /root/.npm/_logs/2024-04-26T16_07_22_901Z-debug-0.log```


[View Deploy details](https://railway.app/project/c1798032-1949-42a4-bc61-f1a2b2bf84e7/service/3f11337c-5e0e-4e0e-9205-95e1ecd050e9?id=0396b855-3308-4253-a9f0-9982c68e13d0)

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

1 Replies

2 years ago

You have a peer dependency issue and will need to fix that.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...