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
I can not install this in my react 18.2.0. Getting errors-
code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/react npm ERR! react@"^18.2.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@">= 15.4.1 < 17.0.0-0" from [email protected] npm ERR! node_modules/react-animate-on-scroll npm ERR! react-animate-on-scroll@"*" 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.
Any solutions?
The text was updated successfully, but these errors were encountered:
currently you need to use npm i --force or npm i --legacy-peer-deps, until the maintainer increase the react version used
npm i --force
npm i --legacy-peer-deps
Sorry, something went wrong.
No branches or pull requests
I can not install this in my react 18.2.0. Getting errors-
code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/react npm ERR! react@"^18.2.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@">= 15.4.1 < 17.0.0-0" from [email protected] npm ERR! node_modules/react-animate-on-scroll npm ERR! react-animate-on-scroll@"*" 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.
Any solutions?
The text was updated successfully, but these errors were encountered: