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
This happens when there is no node-gyp and/or npm available under /usr/local/lib/node_modules/.
Therefore I'd like to propose adding support for process.env.npm_config_node_gyp which is a result of implementing npm install --node-gyp=<path-to-custom-node-gyp> by npm team: npm/npm#4887 .
Thus scripts/install.js of dtrace-provider would have this added:
From jxcore/jxcore#678 it sounds like you fixed this by changing it to call npm-cli.js instead. After the fix for #95 (which was released in dtrace-provider@0.8.3), this library uses the node-gyp in the PATH, which should also take care of fixing this issue.
As we have noticed in jxcore/jxcore#678, the
node-gyp
finding pattern is not sufficient if one would call e.g.:This happens when there is no
node-gyp
and/ornpm
available under/usr/local/lib/node_modules/
.Therefore I'd like to propose adding support for
process.env.npm_config_node_gyp
which is a result of implementingnpm install --node-gyp=<path-to-custom-node-gyp>
by npm team: npm/npm#4887 .Thus
scripts/install.js
ofdtrace-provider
would have this added:The text was updated successfully, but these errors were encountered: