-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
When using NPM as package manager rnv run gets stuck in endless loop #806
Comments
Same issue here npm ERR! A complete log of this run can be found in: npm ERR! code ERESOLVE npm ERR! A complete log of this run can be found in: Error: Command failed with exit code 1: npm install npm ERR! A complete log of this run can be found in: |
@dotted can you please give the canary that we're gonna release in a few minutes a go? The problem should be fixed there |
Unable to test due to a Tested with node v14.19.0 and node v17.8.0 and npm 8.5.5
|
Describe the bug
When
rnv run
tries to install dependencies using NPM it gets stuck in an endless loop as it is unable to resolve peerDependenciesTo Reproduce
legacy-peer-deps=true
is not defined in a.npmrc
file NPM will be reading during installationExpected behavior
Ideally peerDependencies should have been set up correctly, but given that is a problem far outside the scope of renative itself, I'd consider adding a
.npmrc
with the content oflegacy-peer-deps=true
when NPM is used as the package manager as that will allow thenpm install
command to succeed.Screenshots or copy&paste
renative-error.txt
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: