This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
lifecycle: prefer current node in run-script #11626
Closed
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 is a backport of #11204 by @segrey to 2.x branch which I believe was lost.
Fixes: #11175
Fixes: #9253
As mentioned in #11204 (comment) current behaviour of
npm@latest-2x
is really annoying in cases where one can't have nodejs + npm installed globally.For example our internal build farms have different nodejs versions installed to
/opt/nodejs/<ver>
, so we runnpm
with/opt/nodejs/<N>/bin/node /opt/nodejs/<N>/bin/npm
from our build scripts. Everything works fine for projects that run nodejs-0.10 or node-5 that havenpm@1x
andnpm@3x
accordingly and which don't have the bug. But for projects that use nodejs-4 builds might fail if one uses an npm module that needs#!/usr/bin/env node
to run.