-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: npm lock v2 and v3 support #4401
Merged
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
JamesPatrickGill
requested review from
klesniewski,
dotkas and
alexandru-dragomir
February 10, 2023 16:01
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
11 times, most recently
from
February 13, 2023 16:21
df425af
to
8ea0b4f
Compare
admons
previously approved these changes
Feb 14, 2023
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
from
February 14, 2023 11:15
8ea0b4f
to
d8c0665
Compare
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
from
February 17, 2023 14:00
d8c0665
to
920cb69
Compare
5 tasks
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
2 times, most recently
from
February 27, 2023 11:35
a133c49
to
25def97
Compare
orsagie
reviewed
Feb 27, 2023
orsagie
approved these changes
Feb 27, 2023
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
2 times, most recently
from
February 28, 2023 15:14
3ef807a
to
17f44d3
Compare
PeterSchafer
approved these changes
Feb 28, 2023
admons
reviewed
Mar 6, 2023
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
2 times, most recently
from
March 6, 2023 11:56
228780c
to
138388b
Compare
This PR is dependent on the new version of nodejs-lockfile-parser that will be published by this PR snyk/nodejs-lockfile-parser#182 |
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
4 times, most recently
from
March 7, 2023 17:22
6511e07
to
b393ab2
Compare
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
from
March 14, 2023 17:32
b393ab2
to
bf7c8c1
Compare
JamesPatrickGill
force-pushed
the
feat/npm-lock-v2-and-v3-support
branch
from
March 22, 2023 09:27
bf7c8c1
to
921d41b
Compare
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.
What does this PR do?
This adds cli support for
package-lock
versions 2 and 3. These versions have been in use since npm7.Previous support for npm-lock-v2 exists but was using older
dep-tree
logic. This PR also upgrades this to use dep-graph solely.