Repository navigation
[BUG] npm update --dry-run is bloken #9187
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
- It update
node_modules/.package-lock.jsonevent if--dry-runoption is provided. - It produce text and json output if
--dry-runis specified.
Expected Behavior
I am expecting that no changes will be performed in dry-run mode.
I am expecting clear json output.
Steps To Reproduce
- Run
npm up --dry-run --json - See text + json output
- Run
npm up --dry-run --jsononce more - See nothing, this is because
.package-lock.jsonwas updated
Environment
- npm: 11.12.1
- Node.js: v24.14.1
- OS Name:
- System Model Name:
- npm config:
; copy and paste output from `npm config ls` here
Activity
v-kchindam-infy commentedon Apr 3, 2026
Closing: this looks to be similar if not a duplicate of an existing issue #8565 . If you believe your instance is unique, please provide further clarifying details.Please feel free to open the issue persists again
zdm commentedon Apr 3, 2026
Mentioned issue is related to json output.
My issue is also about
--dry-runmake unexpected updates.I have no permissions to re-open issue.
zdm commentedon Apr 6, 2026
@kchindam-infy Could you please reopen it?
cjanssen commentedon May 14, 2026
Can confirm this as well using version 11.8.0. Any call to npm with --dry-run results in changes occuring in the node_modules/.package_lock. Subsequent calls of the same dry run command return 'up to date.'
fix: skip hidden lockfile save on dry run (#9395)
martinrrm commentedon Jul 30, 2026
This has been fixed by #9395 and was released in 11.16.0, please try that version and let us know if the issue is still present.