Move to v2 format for package-lock.json #409
Merged
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.
Description
Please explain the changes you made here.
PR modifies the
package-lock.json
file to the new v2 format which was rolled out with npm v7 back in 10/2020. This is supposed to be better able to give deterministic build results with regards to tree shape. The new lockfile is backwards compatible with npm v6 (which comes with node 14 on some platforms like GH actions), but it's expected that most people will be trending forward to newer versions of npm (which is at v9), that most people won't need to worry about the compatibility.Checklist
Please review this checklist before submitting a pull request.
npm run test:all
)