You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With issues like nodejs/node#19840 and npm/npm#20163 I thought it would be good to start thinking of ways to better handle node-gyp resolution of the Node path as well as how it can have folks like Node and npm rely on it without stepping on each others toes.
With issues like nodejs/node#19840 and npm/npm#20163 I thought it would be good to start thinking of ways to better handle
node-gyp
resolution of the Node path as well as how it can have folks like Node and npm rely on it without stepping on each others toes.File of interest:
lib/find-node-directory.js.
\cc @iarna from npm and @addaleax @MylesBorins from Node.
The text was updated successfully, but these errors were encountered: