Windows release of 0.11.14 breaks native node build with node-gyp

[migounette]

When you get the build release x64 for Windows under
http://nodejs.org/dist/v0.11.14/x64/node-v0.11.14.20140819-x64.msi

node-gyp tries to get the package to the wrong path instead of: http://nodejs.org/dist/v0.11.14/node-v0.11.14.tar.gz

And the version is:

c:_GIT>node --version
v0.11.14-nightly-20140819-pre

And

c:_GIT\webrtc\webrtc-media-factory>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" configure --proxy=http://web-proxy.gre.hp.com:8080
gyp info it worked if it ends with ok
gyp info using node-gyp@0.13.1
gyp info using node@0.11.14-nightly-20140819-pre | win32 | x64
gyp http GET http://nodejs.org/dist/v0.11.14-nightly-20140819-pre/node-v0.11.14-nightly-20140819-pre.tar.gz
gyp http 404 http://nodejs.org/dist/v0.11.14-nightly-20140819-pre/node-v0.11.14-nightly-20140819-pre.tar.gz
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading tarball

[misterdjules]

The plan is to release 0.11.15 very soon, with a x64 Windows binary built correctly this time. That version will supersede 0.11.14. So closing, but feel free to let us know if you need a correct 0.11.14 x64 Windows binary even after 0.11.15 is released.

[JiangJie]

@misterdjules
When will v0.11.15 release? It has been almost one month since your last reply.
My project need v0.11.14 or newer while v0.11.13 can't meet my requirement because of new Set().forEach is undefined and others.

[misterdjules]

@JiangJie I apologize for saying one month ago that 0.11.15 was supposed to be released soon when it hasn't been released yet.

Is using the x86 version an option for you?

Anyway, I'll try to get the 0.11.14 x64 re-uploaded and signed as soon as possible, since I don't know when 0.11.15 will be released. Unfortunately I don't know when that will be possible, but I'll try to keep you informed as much as possible.

In the meantime, I reopened #8460 to track this issue.