Open ghost opened 6 years ago
I just had almost the exact same problem... Stuck after 'Successfully installed Python 2.7'... After waiting for like 20 minutes searching for an ansewer it actually finished...
I just had almost the exact same problem... Stuck after 'Successfully installed Python 2.7'... After waiting for like 20 minutes searching for an ansewer it actually finished...
seems like it was the same for me... thanks it worked.
Well this is pretty annoying .... still waiting for mine to finish.
Getting a similar issue, been sitting on the below for nearly 45 mins...
Lots of reports of errors regarding installations hanging, anything being done ?
Anybody here already saw how to deal with this issue?
See also #123
@jacobq this link do not talk about the solution... it would be this one here: https://github.com/felixrieseberg/windows-build-tools/issues/116
@glaucia86 I just mentioned the other issue because this one may be a duplicate.
Hello all,
Latest Node 10 & 11 have a new stage in their installer that installs all prerequisites for native-addon development. Admittedly it's not 100% bug free, but in-the-field testing is the best way to fix that, so your feedback is welcome. Latest 10 - https://nodejs.org/download/release/latest-v10.x/ Latest 11 - https://nodejs.org/download/release/latest-v11.x/ and version 12 nightlies - https://nodejs.org/download/nightly/
Hi @refack, could you please explain how that is related to this issue? Are you saying that they install the MS build tools automatically, that they no longer require them, or something else? Are you referring to https://github.com/nodejs/node/pull/22645? In that case, I think that doesn't affect nvm-windows
users since it requires opting in.
@refack I noticed that I install in my machine Node.js 10 and when I tried to install node-gyp and windows build tools I had some issues.. If you want to I can relate for you here. Should I do make a downgrade of my actual version (Node.js -> 10) to Node.js 8.x?
@jacobq the version 5 of windows build tools are bugged. Yesterday I used the version 4 and installed it perfectly.
Hi @refack, could you please explain how that is related to this issue? Are you saying that they install the MS build tools automatically, that they no longer require them, or something else?
I admit it doesn't relate directly to this issue, but IMHO it relates to the end goal of installing Windows build tools.
Are you referring to nodejs/node#22645? In that case, I think that doesn't affect
nvm-windows
users since it requires opting in.
You are right, ATM it's only available for users who choose to install with the .msi
installer. We are considering deploying the boxstarter script via the zip, so other users could benefit from it as well.
Edit: opened https://github.com/nodejs/node/pull/24233
@refack I noticed that I install in my machine Node.js 10 and when I tried to install node-gyp and windows build tools I had some issues.. If you want to I can relate for you here.
@glaucia86 I would appreciate if you would open an issue in nodejs/node
The updates mentioned by @refack to the Node installer for native-addon pre-requisites ended up getting reverted.
s ended up getting reverted.
Just for node@10, and just temporarily. Because node is 10 LTS we didn't want the tools in the new releases, until we ironed out the kinks. They are still available in node@11 releases. And now we have a streamlined versioned in the works - https://github.com/nodejs/node/pull/24677
Hi,
I'm trying to get native packages running since two weeks now.. without success.
System: Win7 x64
I definitely have an internet connection as all my firewalls are down.