Upgrade package-lock.json to lockfile@2 #1659
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will do a prerelease of Commander v9 soon, but no hurry on this PR. It does not need to be in it. |
shadowspawn
added
the
pending release
shadowspawn
removed
the
pending release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Problem
npm 6 and 8 use different formats for
package-lock.json. Problems switching. Which shall we use?Related: #1658
Solution
Go for the version that works nicely with Node.js v16 so convenient for developers (maintainers!) working on new versions.
Not upgrading TypeScript yet, as generates warnings from eslint.
Not upgrading eslint or any of the eslint related dependencies yet, waiting for eslint 8 compatible versions.
ChangeLog
package-lock.jsontolockfile@2format.