-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
deps: pacote@13.6.1, @npmcli/run-script@4.1.0 #5049
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
nlf
force-pushed
the
nlf/deps-run-script-4.1.0
branch
from
June 21, 2022 21:24
09b23b8
to
26a2855
Compare
nlf
force-pushed
the
nlf/deps-run-script-4.1.0
branch
from
June 21, 2022 21:50
26a2855
to
2841706
Compare
fritzy
approved these changes
Jun 21, 2022
Merged
This was a breaking change in arborist, because it raised the engines requirement from 12.13 to 12.22 due to npm/run-script#76. Possible solutions:
|
ljharb
referenced
this pull request
in ljharb/npm-lockfile
Sep 20, 2022
ljharb
added a commit
to ljharb/aud
that referenced
this pull request
Sep 20, 2022
Specifically, updating to `@npmcli/run-script` v4, which requires node-gyp 9, which requires node v12.22, instead of v12.13 See npm/cli#5049
ljharb
added a commit
to ljharb/get-dep-tree
that referenced
this pull request
Sep 27, 2022
Pin both due to a breaking change; see npm/cli#5049 (comment) / npm/run-script#76
ljharb
added a commit
to ljharb/ls-publishers
that referenced
this pull request
Oct 27, 2022
…er`, `yargs` Pin arborist and pacote due to a breaking change; see npm/cli#5049 (comment) / npm/run-script#76
ljharb
added a commit
to ljharb/ls-publishers
that referenced
this pull request
Oct 27, 2022
… `yargs` Pin arborist and pacote due to a breaking change; see npm/cli#5049 (comment) / npm/run-script#76
ljharb
added a commit
to ljharb/publishers
that referenced
this pull request
Oct 28, 2022
…but pin due to a breaking change; see npm/cli#5049 (comment) / npm/cli#5049 (comment)
2 tasks
ljharb
added a commit
to ljharb/aud
that referenced
this pull request
Dec 19, 2022
Fixed in node-gyp v9.3.1, in nodejs/node-gyp#2771 See: - npm/run-script#76 - npm/cli#5049 (comment)
ljharb
added a commit
to ljharb/npm-lockfile
that referenced
this pull request
Dec 19, 2022
Fixed in node-gyp v9.3.1, in nodejs/node-gyp#2771 See: - npm/run-script#76 - npm/cli#5049 (comment)
ljharb
added a commit
to ljharb/get-dep-tree
that referenced
this pull request
Dec 19, 2022
Fixed in node-gyp v9.3.1, in nodejs/node-gyp#2771 See: - npm/run-script#76 - npm/cli#5049 (comment)
ljharb
added a commit
to ljharb/ls-publishers
that referenced
this pull request
Dec 19, 2022
Fixed in node-gyp v9.3.1, in nodejs/node-gyp#2771 See: - npm/run-script#76 - npm/cli#5049 (comment)
This was fixed in nodejs/node-gyp#2771 and released in node-gyp v9.3.1. Thanks! |
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.
No description provided.