-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 release
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
lockfileVersion
set to 3
in package-lock.json
is downgraded back to 2
when running npm update
.
Expected Behavior
I think the lockfile version should be preserved as is, not downgraded.
Steps To Reproduce
- Set the
lockfileVersion
property to3
in apackage-lock.json
file. (You have to do it manually for now as the newlockfile-version
option doesn’t yet really work.1) - Run
npm install
, which deletes the legacydependencies
object and upgrades the hidden lockfile. - Run
npm update
and you’ll see how the lockfile version is downgraded.
Environment
- OS: MacOS 11.6
- Node: 16.12.0, 17.0.1
- npm: 8.1.0
Footnotes
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 release