-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[BUG] npm update --depth breaks dependencies #607
Comments
Looks like I've prepared duplicated issue What / WhyCommand When
Where
HowCurrent BehaviorIt loses Steps to Reproduce
Expected BehaviorI expect that this action should keep ReferencesPossibly related to #944 |
I'm also experiencing that |
I found out that the dev flag is restored after reinstalling the node modules ( |
I see the same issue of loosing the In my case an other dependency adds "@types/node" as dependency but at my project has it as dev dependency: package.json of dependency "a":
my project:
after edit: |
npm If your bug is preproducible on If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo Closing: This is an automated message. |
What / Why
When
npm --depth 9999 update
Where
How
Current Behavior
npm ls
reports a lot of missing/unmet dependencies, for example:Steps to Reproduce
npm init
npm i -D @semantic-release/exec
npm --depth 9999 update
Expected Behavior
package.json
file of their parent or anynpm-shrinkwrap.json
of their ancestor.package-lock.json
and proceed to resolve all dependencies, install/update/remove as necessary, and then update the lockfile with the resolved tree.Who
References
The text was updated successfully, but these errors were encountered: