Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing Problem unable to resolve dependency tree #562

Open
Gercekefsane opened this issue Sep 6, 2021 · 3 comments
Open

Installing Problem unable to resolve dependency tree #562

Gercekefsane opened this issue Sep 6, 2021 · 3 comments

Comments

@Gercekefsane
Copy link

Hello,
When you try to install you will get this error. How can I fix it ?

`PS C:\Users\Administrator\Desktop\atlanta1> npm install --production
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: atlantabot@4.12.0
npm ERR! Found: discord.js@13.2.0-dev
npm ERR! node_modules/discord.js
npm ERR! discord.js@"discordjs/discord.js" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer discord.js@"^12.0.0" from discord-paginationembed@2.1.0
npm ERR! node_modules/discord-paginationembed
npm ERR! discord-paginationembed@"^2.1.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\Administrator\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Local\npm-cache_logs\2021-09-06T16_06_34_842Z-debug.log`

@SickProdigy
Copy link

Clone of issue: #524

@SickProdigy SickProdigy mentioned this issue Sep 7, 2021
@SickProdigy
Copy link

4.11 doesn't have this dependency problem. But has some others that can be ignored if you'd like to try it. I have tested pretty well. And works out of the box. Looking for a fix for this issue myself on 4.12.

@S1mp1yDucky
Copy link

Enter npm install --force and it should fix the problem!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants