-
Notifications
You must be signed in to change notification settings - Fork 332
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
Check resolutions
#427
Labels
Comments
Great suggestion! |
need this |
Need this feature for sure. Its real usecase. |
try |
Bump. I kinda need this for my tools using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
resolutions
field of package.json contains version specifications for modules-of-modules. I would like it if npm-check-updates could check these dependencies as well.The two main use-cases for the field are to either pin a dependency to a specific version (e.g., for compatibility) or to keep the versions in sync across modules (e.g., for smaller webpack bundles).
I'm interested in use-case 2, and for me that means I have to manually update the
resolutions
field to matchdependencies
after everyncu
. It would be nice ifncu
could do it for me.To support use-case 1, it shouldn't check this field by default; it needs to be opt-in, so a flag and/or a configuration option would be needed.
The text was updated successfully, but these errors were encountered: