-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 2secondary priority issuesecondary priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 releasecmd:execrelated to `npx`related to `npx`
Description
Current Behavior:
npx node-gyp@8
runs the oldernode-gyp
7.1.2 that is bundled withnpm
./home/[me]/n-prefix/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
Same result if doing plain npx node-gyp
. The latest version is v8.0.0, but v7.1.2 is used instead. Happens even if node-gyp
v8 is installed globally, and no node-gyp
is installed in the location npx
is run from.
Expected Behavior:
A separate npx
-specific copy of node-gyp
v8 should run. Or when node-gyp
v8 is installed globally, that could be used.
Steps To Reproduce:
npx node-gyp
or npx node-gyp@8
or npx [email protected]
, etc.
Environment:
- OS: Ubuntu 20.04, macOS 10.15.7 Catalina, Windows 10
- Node: v14.16.1, v16.0.0-nightly2021041040ace47396
- npm: 7.9.0
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 2secondary priority issuesecondary priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 releasecmd:execrelated to `npx`related to `npx`