fix!: stop setting NODE env var and resolving node path via whichnode#9039
Draft
owlstronaut wants to merge 1 commit intolatestfrom
Draft
fix!: stop setting NODE env var and resolving node path via whichnode#9039owlstronaut wants to merge 1 commit intolatestfrom
owlstronaut wants to merge 1 commit intolatestfrom
Conversation
BREAKING CHANGE: npm will no longer attempt to resolve the path to node via whichnode, and will not set the NODE environment variable. This can affect scripts that rely on the NODE environment variable or expect npm to resolve the path to node.
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
1 participant
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.
BREAKING CHANGE: npm will no longer attempt to resolve the path to node via whichnode, and will not set the NODE environment variable. This can affect scripts that rely on the NODE environment variable or expect npm to resolve the path to node.
closes npm/statusboard#1070