-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opposite of --ensure, and is --ensure still useful? #1216
Comments
Thinking about this further, if the Thoughts? |
That's correct. It's unconditionally set in lib/configure.js.
I don't think so. What good would it do?
I suppose. It could piggyback on the remove command. |
I ran into this because we were testing module.js:598
return process.dlopen(module, path._makeLong(filename));
^
Error: The module '/space/jenkins-local/workspace/ibm-node8-appmetrics/ARCH/x64/CC/gcc48/OS/linux/label/build/node-v8.0.0-linux-x64/lib/node_modules/appmetrics/appmetrics.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 55. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing When running in CI I always want to redownload the headers. If the " |
If you're providing a path to a header tarball to install, you probably want it to always be re-installed. Fixes: nodejs#1216
I was looking for a way to force
node-gyp
to re-download the headers even if the directory already exists in$npm_config_devdir/$node_version
, and I found--ensure
, which seems to do the opposite.As I understand it,
node-gyp
doesn't download the headers unless the directory is missing, so--ensure
is the default behaviour. Am I missing something? Is there a--always-redownload
option (and should there be)?Obviously as a workaround you can do this before the
node-gyp rebuild
ornpm install
:The text was updated successfully, but these errors were encountered: