when I using this command to install sass-loader in my project:
npm install sass-loader#12.4.0
show error like this:
➜ crx-selection-translate git:(6.x-master) ✗ npm install sass-loader#12.4.0
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined#undefined
npm ERR! Found: webpack#1.15.0
npm ERR! node_modules/webpack
npm ERR! dev webpack#"^1.13.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack#"^5.0.0" from sass-loader#12.4.0
npm ERR! node_modules/sass-loader
npm ERR! sass-loader#"12.4.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 /Users/xiaoqiangjiang/.npm/eresolve-report.txt for a full report.
why did this happen? what should I do to fix this problem? is it possible to auto resolve and fix the dependencies? I really did not know which version should I use, and I still did not know the dependencies matrix, is it possible to let the npm to find the most suitable dependencies and auto install and fix?
I found a solution on dev.to
This worked for me
npm install -D sass-loader#^10 sass
Related
I just cloned a React application from Git that doesn't have node_modules on it. I try to install with command npm install but unable to do it. Following error occurs when installing the npm.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: fuse-react-app#2.0.0
npm ERR! Found: date-fns#2.0.0-alpha.26
npm ERR! node_modules/date-fns
npm ERR! date-fns#"2.0.0-alpha.26" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer date-fns#"2.0.0-alpha.21" from #date-io/date-fns#1.0.1
npm ERR! node_modules/#date-io/date-fns
npm ERR! #date-io/date-fns#"1.0.1" 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\...\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\...\AppData\Local\npm-cache\_logs\2022-04-24T12_44_19_589Z-debug-0.log
I even tried with npm install --legacy-peer-deps but doesn't work. How can I fix this issue?
TL;DR
A possible solution to this problem is setting the version of date-fns to 2.0.0-alpha.21.
Full Answer
To fix your issue, you can change the version of date-fns.
To do this, follow these steps.
In package.json, edit the version of date-fns with the following:
{
"dependencies": {
"date-fns": "2.0.0-alpha.21"
}
}
Save the package.json file, and run the following command in the same directory as package.json.
$ npm install
Your dependencies should install successfully.
Conclusion
In conclusion, you need to change the version of date-fns to 2.0.0-alpha.21.
When I run prisma generate I get:
Prisma schema loaded from prisma/schema.prisma
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: site#0.1.0
npm ERR! Found: react#17.0.2
npm ERR! node_modules/react
npm ERR! react#"^17.0.2" from the root project
npm ERR! peer react#"^17.0.2" from next#11.1.2
npm ERR! node_modules/next
npm ERR! next#"^11.1.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"17.0.1" from react-dom#17.0.1
npm ERR! node_modules/react-dom
npm ERR! react-dom#"17.0.1" 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! A complete log of this run can be found in:
I have tried the command with --legacy-peer-deps, but it says:
unknown or unexpected option: --legacy-peer-deps
I don't have any problems installing everything, I don't have any problems running the app. I also deleted the node_modules folder & yarn.lock file and tried a new yarn install --legacy-peer-deps but I'm still getting the same error. Also tried the aforementioned with npm. Now not sure what I could do anymore.
npm install #prisma/client fixed it for me
In React Native application to make a navigation need to install #react-navigation/stack using npm install #react-navigation/stack and I have tried it and failed each and every times.
NPM version: 7.19.1
Node version: v15.14.0
Expo version: 4.8.1
After running npm install #react-navigation/stack this command I have faced the below error is given,
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined#undefined
npm ERR! Found: #react-navigation/native#3.8.4
npm ERR! node_modules/#react-navigation/native
npm ERR! #react-navigation/native#"^3.8.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer #react-navigation/native#"^6.0.0" from #react-navigation/stack#6.0.1
npm ERR! node_modules/#react-navigation/stack
npm ERR! #react-navigation/stack#"*" 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 /home/imdadul/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/imdadul/.npm/_logs/2021-08-04T07_46_39_555Z-debug.log
Note: Please concern the attached file and who have knowledge about this will be helpful to help me. Advanced Thanks!
You have dependency conflict which means that the dependency is incorrect and potentially broken. You could try to run the command with --force, or --legacy-peer-deps and see if that helps.
npm install #react-navigation/stack --force
or
npm install #react-navigation/stack --legacy-peer-deps
Sometimes removing the node_modules and package-lock.json file and run the command npm install #react-navigation/stack or try npm cache clean --force can work.
I cloned Vue2Vis and executed the command
npm install --save #vue2vis/graph2d vis-data moment
as stipulated in the packages/graph2d/README.md file. Here is the result:
npm install --save #vue2vis/graph2d vis-data moment
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: #vue2vis/graph2d#1.0.1-alpha.0
npm ERR! Found: uuid#7.0.3
npm ERR! node_modules/uuid
npm ERR! dev uuid#"^7.0.0" from #vue2vis/graph2d#1.0.1-alpha.0
npm ERR! packages/graph2d
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer uuid#"^3.4.0" from vis-timeline#7.3.4
npm ERR! node_modules/vis-timeline
npm ERR! vis-timeline#"^7.3.4" from #vue2vis/graph2d#1.0.1-alpha.0
npm ERR! packages/graph2d
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 /Users/erlebach/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/erlebach/.npm/_logs/2021-06-21T22_11_11_109Z-debug.log
I thought this procedure was foolproof! :-) Does anybody have any insight to help me out? Thanks.
It looks like vis-data's latest release (7.x) is now incompatible with graph2d. The other errors in your stacktrace seem related to vis-data 7.
Specifying vis-data#^6.3.0 in the installation worked without errors:
$ npm install --save #vue2vis/graph2d vis-data#^6.3.0 moment
added 15 packages, and audited 16 packages in 4s
3 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
as the title suggests I'm trying to install DateTimePicker and I get this error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined#undefined
npm ERR! Found: react#16.13.1
npm ERR! node_modules/react
npm ERR! react#"16.13.1" from the root project
npm ERR! peer react#">=16.8.3" from #react-native-community/datetimepicker#3.0.4
npm ERR! node_modules/#react-native-community/datetimepicker
npm ERR! #react-native-community/datetimepicker#"3.0.4" from the root project
npm ERR! 1 more (react-native)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"17.0.1" from react-native-windows#0.64.5
npm ERR! node_modules/react-native-windows
npm ERR! peer react-native-windows#">=0.62" from #react-native-community/datetimepicker#3.0.4
npm ERR! node_modules/#react-native-community/datetimepicker
npm ERR! #react-native-community/datetimepicker#"3.0.4" 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\robbi\AppData\Local\npm-cache\eresolve-report.txt for a full report.
How can I do?
Sorry for the stupid question but I'm still studying ..
If you are using expo download your dependency through
expo install #react-native-community/datetimepicker
If you have used yarn or npm for that some dependencies might have a conflict with each other (because of incompatibility issues) whereas through expo install it will install the respective version of the package according to your expo version