-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
proposal: --deep
/ --depth=XX
option.
#154
Comments
--deep
/ --depth
option.--deep
/ --depth=XX
option.
Thanks! That would be a nice addition. It would not be hard to call ncu recursively on nested package.json's. It may require some UI thoughtfulness to have an understandable output. I am putting this at low priority unless others chime in and say this is a strongly desired feature. |
Perhaps it should mix the current output style and that of
Use Options should include listing everything (regardless of whether it is behind or not), or filtering just the lines that have a outdated dependency. In the filtering case, you would probably want to keep parents of outdated deps in the tree (but give them some light-gray "disabled" color that tells users to ignore them). Probably the first step is to create a JSON output that captures all the details, then worry about how to format that. |
OK, |
|
|
This is now resolved, thanks to #785 🎉 |
not working with pnpm edit: d'oh. same result with npm. |
This would traverse the entire dependency tree and find ALL outdated dependencies throughout the entire graph. This would warn you if you are relying on a library that is not actively maintained and has not updated it's own dependencies in a long time. Hopefully this would drive some users to get involved filing PR's against their dependencies even if they are just simple
bump XXX
PR's.There is is some value in deeply traversing the production dependencies of your dev dependencies, but maybe not dev dependencies of your dev dependencies.
The text was updated successfully, but these errors were encountered: