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

[Bug] npm install returns error: unable to resolve dependency tree #11

Closed
FatihBekdemir opened this issue Aug 4, 2022 · 1 comment
Closed

Comments

@FatihBekdemir
Copy link

Version

1.5.1

Reproduction link

https://github.com/creativetimofficial/now-ui-kit-react

Operating System

Windows

Device

Lenovo

Browser & Version

Chrome

Steps to reproduce

  1. Clone the now-ui-kit-react repo from github page, or from the https://www.creative-tim.com/product/now-ui-kit-react page.
  2. Open a terminal where the project folder is located.
  3. run npm install

What is expected?

It should start loading node_modules folder with the expected modules inside.

What is actually happening?

It returns the error below:

npm ERR! 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@"^16.5.0 || ^17.0.0" from [email protected]
npm ERR! node_modules/react-datetime
npm ERR! react-datetime@"3.1.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\X\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\X\AppData\Local\npm-cache_logs\2022-08-04T12_31_35_183Z-debug-0.log


Solution

First, running this command:
=> npm install --legacy-peer-deps
Then, normal npm install
=> npm install

it will give you this response:
added 1810 packages, and audited 1811 packages in 4m
209 packages are looking for funding
run npm fund for details
12 high severity vulnerabilities

=> npm start

Additional comments

@sajadevo
Copy link
Contributor

This issue is fixed on v1.5.2.

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

2 participants