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

NextJS Blog Starter: React Dependency conflict #78

Open
marcKsl opened this issue Feb 19, 2023 · 0 comments
Open

NextJS Blog Starter: React Dependency conflict #78

marcKsl opened this issue Feb 19, 2023 · 0 comments

Comments

@marcKsl
Copy link

marcKsl commented Feb 19, 2023

I tried to install the Blog starter with NextJs and Strapi but got the following error:

ERR! A complete log of this run can be found in: npm ERR! /Users/YOUR_USER/.npm/_logs/2023-02-19T09_43_45_854Z-debug-0.log This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: Command failed with exit code 1: npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: my-next-blog@1.0.3 npm ERR! Found: react@17.0.0 npm ERR! node_modules/react npm ERR! react@"17.0.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^17.0.2" from next@11.1.4 npm ERR! node_modules/next npm ERR! next@"^11.0.0" from the root project npm ERR! peer next@">=10.2.0" from eslint-config-next@11.1.4 npm ERR! node_modules/eslint-config-next npm ERR! dev eslint-config-next@"^11.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! npm ERR! For a full report see: npm ERR! /Users/YOUR_USER/.npm/_logs/2023-02-19T09_43_45_854Z-eresolve-report.txt

It seems that that NextJs frontend requires a higher version of the React Package than the Strapi backend does.
I would suggest updating the dependencies, so that everything works again out of the box.

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

1 participant