Skip to content
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.

fix: always set originalLockfileVersion when doing shrinkwrap reset #339

Merged
merged 1 commit into from
Oct 27, 2021

Conversation

lukekarrys
Copy link
Contributor

Fix: npm/cli#3899

A shrinkwrap reset without specifying a lockfile version was triggering
an old lockfile warning due to the originalLockfileVersion not being set
prior to checking whether the lockfile was old.

@lukekarrys lukekarrys force-pushed the lk/empty-update-old-lockfile branch 2 times, most recently from 4fc3a53 to 6429b9d Compare October 21, 2021 20:44
Fix: npm/cli#3899

A shrinkwrap reset without specifying a lockfile version was triggering
an old lockfile warning due to the originalLockfileVersion not being set
prior to checking whether the lockfile was old.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] npm update --dev triggers npm WARN old lockfile each time
2 participants