fix: suggest --allow-scripts for global installs in unreviewed-scripts warnings#9469
Merged
owlstronaut merged 4 commits intoJun 3, 2026
Merged
Conversation
…s in unreviewed-scripts warnings
ljharb
reviewed
Jun 2, 2026
ljharb
reviewed
Jun 2, 2026
owlstronaut
reviewed
Jun 3, 2026
owlstronaut
approved these changes
Jun 3, 2026
Contributor
|
🎉 Backport to |
This file contains hidden or 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
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.
The unreviewed-scripts warning told users to run
npm approve-scripts, which fails on global installs and npx/exec because there's no project package.json to write to. The warnings now checknpm.globaland point global users at the--allow-scriptsflag and theallow-scripts.npmrc setting instead.Covers the install warning (reify-output), the rebuild advisory warning, and the strict-allow-scripts preflight error. Also updates the approve-scripts docs.
References
Fixes #9457