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
Node Version: any (tested with v4.8.3-proposal and v6.10.3-proposal)
CitGM Version: 1.11.10
Platform: any (tested on macOS Sierra)
While fixing #400 (comment) in the citgm-abi-smoker job, I noticed that native modules like bcrypt were trying to download the headers from nodejs.org, despite showing that they were passed the --nodedir citgm option. citgm-smoker also does an export npm_config_nodedir=/path/to/node, and doesn't have this problem. I added the export to citgm-abi-smoker, and the next build doesn't have this problem either.
I assume it's just that the option isn't being passed through for some reason.
I can replicate manually by doing:
git checkout v6.10.3-proposal
make -j4 binary # Builds node and packs into local tarball
tar -xf node-*.tar.gz
cd$PWD/node-*/bin &&export PATH="$PWD:$PATH"&&cd -
npm i -g citgm
citgm -v silly --nodedir $PWD bcrypt # Failsexport npm_config_nodedir="$PWD"
citgm -v silly --nodedir $PWD bcrypt # Passes
citgm -v silly bcrypt # Also passes
We currently pass --nodedir as an argument to `npm install`. However this
doesn't work for modules like bcrypt whose `npm test` script starts with
an `npm install`.
Fixes: nodejs#401
gibfahn
added a commit
to gibfahn/citgm
that referenced
this issue
May 1, 2017
We currently pass --nodedir as an argument to `npm install`. However
this doesn't work for modules like bcrypt whose `npm test` script starts
with an `npm install`. Set the environment variable instead.
Fixes: nodejs#401
We currently pass --nodedir as an argument to `npm install`. However
this doesn't work for modules like bcrypt whose `npm test` script starts
with an `npm install`. Set the environment variable instead.
Fixes: nodejs#401
gibfahn
added a commit
to gibfahn/citgm
that referenced
this issue
Feb 19, 2018
We currently pass --nodedir as an argument to `npm install`. However
this doesn't work for modules like bcrypt whose `npm test` script starts
with an `npm install`. Set the environment variable instead.
Fixes: nodejs#401
v4.8.3-proposal
andv6.10.3-proposal
)While fixing #400 (comment) in the
citgm-abi-smoker
job, I noticed that native modules like bcrypt were trying to download the headers from nodejs.org, despite showing that they were passed the--nodedir
citgm option.citgm-smoker
also does anexport npm_config_nodedir=/path/to/node
, and doesn't have this problem. I added theexport
tocitgm-abi-smoker
, and the next build doesn't have this problem either.I assume it's just that the option isn't being passed through for some reason.
I can replicate manually by doing:
Bcrypt output:
The text was updated successfully, but these errors were encountered: