install via git for language: node#3719
Merged
Merged
Conversation
this avoids trying to play catch-up with whatever preparation commands npm does when installing from `npm i git+...` (which differs from `npm i a/dir`) the latter does not run any preparation commands leading to broken installs the previous command we were using was suggested by the npm devs, however some of the options that it was using are no longer part of npm itself and npm 12.x errors on unknown options
asottile
marked this pull request as ready for review
July 15, 2026 20:31
asottile
enabled auto-merge
July 15, 2026 20:32
|
Will there be a release soon containing this fix? |
Member
Author
|
I plan to never release this! hahaha |
|
You can do |
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
3 participants
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.
this avoids trying to play catch-up with whatever preparation commands npm does when installing from
npm i git+...(which differs fromnpm i a/dir) the latter does not run any preparation commands leading to broken installsthe previous command we were using was suggested by the npm devs, however some of the options that it was using are no longer part of npm itself and npm 12.x errors on unknown options
this ~technically breaks compatibility on windows some 2019-era npm versions but it's big 26 so...
resolves #3517