Alternative environment variable due to warning on npm_config_nodedir #3163
Description
See title.
Somewhere since [email protected], npm now warns on seeing 'unknown' configuration options.
Setting nodedir in your npmrc (or setting the environment variable npm_config_nodedir) gives us a warning that nodedir is not supported, and will be an error Real Soon (tm):
npm warn Unknown user config "nodedir". This will stop working in the next major version of npm.
Provided I want to set up the nodedir for scripts that end up calling scripts than end up calling scripts than run npm 1, how will I be able to set up a simple environment variable that allow node-gyp to find the relevant node files in the future when the current approach will no longer work?
Footnotes
-
So I don't have control over the actual invocation of the
npm, and therefore can't simply pass an option. ↩