-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Support for package resolutions #1296
Comments
@mihaiblaga89 how to test this? |
@pauliusguzas take an app as example. I'll take template-starter which is not exactly a good example because RNV will not change the template itself but it will print the warnings. We have a
but, if you have a package.json resolutions that specifies next to, let's say 13.5.5 you should see this
|
Tested on template-starter with
|
this is what I get on app-harness
|
I have added 14.0.3 version to renative.json, 14.0.2 to resolutions in package.json and left 14.0.4 in package json dependencies
Then did
When no resolutions are used I am getting same issue on app harness as in #1296 (comment) first point |
If there are package.json resolutions present for package X don't inject it in dependencies with the version defined in renative.json but use the one from resolutions instead
The text was updated successfully, but these errors were encountered: