Node-gyp rebuild not downloading headers on nightly Node 8.0.0 build

[sjanuary]

node-gyp rebuild seems to be looking in the wrong place when trying to download the Node.js headers for the latest nightly 8.0.0 build.

gyp ERR! stack Error: 404 response downloading https://nodejs.org/dist/v8.0.0-nightly20170410b470a85f07/node-v8.0.0-nightly20170410b470a85f07.tar.gz
gyp ERR! stack     at Request.<anonymous> (/home/sian/node-v8.0.0-nightly20170410b470a85f07-linux-x64/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:210:14)
gyp ERR! stack     at emitOne (events.js:120:20)
gyp ERR! stack     at Request.emit (events.js:210:7)
gyp ERR! stack     at Request.onRequestResponse (/home/sian/node-v8.0.0-nightly20170410b470a85f07-linux-x64/lib/node_modules/npm/node_modules/request/request.js:986:10)
gyp ERR! stack     at emitOne (events.js:115:13)
gyp ERR! stack     at ClientRequest.emit (events.js:210:7)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:550:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:115:23)
gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:439:20)
gyp ERR! stack     at emitOne (events.js:115:13)
gyp ERR! System Linux 4.4.0-66-generic
gyp ERR! command "/home/sian/node-v8.0.0-nightly20170410b470a85f07-linux-x64/bin/node" "/home/sian/node-v8.0.0-nightly20170410b470a85f07-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/sian/node_modules/appmetrics
gyp ERR! node -v v8.0.0-nightly20170410b470a85f07
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok 

It seems to be looking in https://nodejs.org/dist/ instead of https://nodejs.org/download/nightly/

[bnoordhuis]

From side-channel discussion, process.release points to the right URLs:

$ node -p process.release
{ name: 'node',
 sourceUrl: 'https://nodejs.org/download/nightly/v8.0.0-nightly20170410b470a85f07/node-v8.0.0-nightly20170410b470a85f07.tar.gz',
 headersUrl: 'https://nodejs.org/download/nightly/v8.0.0-nightly20170410b470a85f07/node-v8.0.0-nightly20170410b470a85f07-headers.tar.gz' }

[bnoordhuis]

After some more discussion it turns out it's caused by NVM_*_MIRROR environment variables. #1170 should make that easier to spot.

[sjanuary]

It's working for me after unsetting related variables so I'm going to close this issue. Thanks for your help @bnoordhuis