We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
shimak@Shimaks-MBP get-it % npm install --save @moxy/next-common-files npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: get-it@undefined npm ERR! Found: [email protected] npm ERR! node_modules/next npm ERR! next@"12.0.7" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer next@">=8 <=11" from @moxy/[email protected] npm ERR! node_modules/@moxy/next-common-files npm ERR! @moxy/next-common-files@"*" 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/shimak/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in: npm ERR! /Users/shimak/.npm/_logs/2022-01-04T09_47_07_351Z-debug.log
The text was updated successfully, but these errors were encountered:
No branches or pull requests
shimak@Shimaks-MBP get-it % npm install --save @moxy/next-common-files
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: get-it@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/next
npm ERR! next@"12.0.7" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@">=8 <=11" from @moxy/[email protected]
npm ERR! node_modules/@moxy/next-common-files
npm ERR! @moxy/next-common-files@"*" 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/shimak/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/shimak/.npm/_logs/2022-01-04T09_47_07_351Z-debug.log
The text was updated successfully, but these errors were encountered: