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
Cloned project:
leezilla@somemachine ~/codez> git clone git@github.com:Sila-Money/sila-sdk-demo.git Cloning into 'sila-sdk-demo'... remote: Enumerating objects: 123, done. remote: Counting objects: 100% (123/123), done. remote: Compressing objects: 100% (77/77), done. remote: Total 1037 (delta 55), reused 72 (delta 33), pack-reused 914 Receiving objects: 100% (1037/1037), 298.95 KiB | 1.51 MiB/s, done. Resolving deltas: 100% (626/626), done. leezilla@somemachine ~/codez> cd sila-sdk-demo leezilla@somemachine ~/c/sila-sdk-demo (master)> npm i npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: sila-sdk-demo@0.2.0 npm ERR! Found: react@17.0.1 npm ERR! node_modules/react npm ERR! react@"^17.0.1" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.14.0" from react-test-renderer@16.14.0 npm ERR! node_modules/react-test-renderer npm ERR! dev react-test-renderer@"^16.13.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 /Users/leezilla/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /Users/leezilla/.npm/_logs/2021-03-17T00_44_00_525Z-debug.log
The text was updated successfully, but these errors were encountered:
Same here. Need to force though 😞
Sorry, something went wrong.
No branches or pull requests
Cloned project:
The text was updated successfully, but these errors were encountered: