You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If my package.json has a dependency, depAbc, with version 4.0.1. NCU would upgrade to the latest version < 5.0.0. I realize this is the same as specifying ^4.0.1. So maybe ncu -u would change the package.json to be:
depAbc: ^4.7.5
The text was updated successfully, but these errors were encountered:
If you have a dependency "depAbc": "4.0.1", ncu will upgrade to the latest version (even if > 5.0.0). ncu will always upgrade to the latest (or --greatest) version. If you are not wanting to force versions to the latest, it is generally assumed that you are wanting to stay within your version constraints, and should just use npm update to get the latest version within the specified constraint. Does that answer your question?
npm update updates package.json only if (1) given package is installed in node_modules and (2) is installed at version lower than latest as supported by range.
In many cases it'll be already installed in node_modules at latest supported, that won't force an update to package.json. Clearing node_modules also doesn't help as then (1) is not satisfied
If my package.json has a dependency, depAbc, with version 4.0.1. NCU would upgrade to the latest version < 5.0.0. I realize this is the same as specifying ^4.0.1. So maybe ncu -u would change the package.json to be:
The text was updated successfully, but these errors were encountered: