Skip to content

fix: improve quoting for run-script arguments#52

Closed
rhendric wants to merge 1 commit into
npm:latestfrom
rhendric:fix/npm-18670
Closed

fix: improve quoting for run-script arguments#52
rhendric wants to merge 1 commit into
npm:latestfrom
rhendric:fix/npm-18670

Conversation

@rhendric

Copy link
Copy Markdown
Contributor

Importing from npm/npm#18709, where there is a longish conversation about breaking changes and wanting this behavior in npm ‘eventually’... npm@7 now?

@rhendric rhendric requested a review from a team as a code owner August 16, 2018 03:58
@zkat zkat added the semver:major backwards-incompatible breaking changes label Aug 20, 2018

@zkat zkat left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provisional 👍 until npm@7 rolls around, since we did approve this for the last round and missed the npm@6 boat. Sorry!

@isaacs

isaacs commented Sep 11, 2020

Copy link
Copy Markdown
Contributor

npm/run-script#3

@isaacs isaacs closed this Sep 11, 2020
Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
…writes

fix: atomic credential file writes to prevent corruption on crash (fixes npm#42)
github-actions Bot added a commit to Kevinlee7250/cli that referenced this pull request Jun 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Release 7.x work is associated with a specific npm 7 release semver:major backwards-incompatible breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants