-
Notifications
You must be signed in to change notification settings - Fork 26
Error: 404 response downloading https://nodejs.org/dist/v7.0.0-pre8/node-v7.0.0-pre8.tar.gz #28
Comments
@jianchun Any ideas? This is stopping me getting started with my project. |
When you launch the command line, did you launch "Node.js (chakra) command prompt"? It is supposed to set an environment variable, then your command will run a custom version of node-gyp. E.g., my command window
Your log shows running a different node-gyp, which does not work with node-chakra:
|
@jianchun Here is my console: and the full log:
|
@georgeedwards I was on v6.0.0-... I uninstalled mine and installed v7.0.0-pre8 and that env variable is gone. @munyirik Do you know if we removed that intentionally or there was a merge error? |
I don't think npm_config_node_gyp has anything to do with it. I just tried to reproduce the problem and even though it's not set, I can build uwp.node ... C:\Users\munyirik\Desktop\temp\temp>npm install uwp --target_arch=arm
> uwp@1.0.2 install C:\Users\munyirik\Desktop\temp\node_modules\uwp
> node-gyp rebuild
C:\Users\munyirik\Desktop\temp\node_modules\uwp>if not defined npm_config_node_gyp (node "C:\Program Files\NodejsUwp\Console\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
uwp.cc
win_delay_load_hook.cc
C:\Users\munyirik\Desktop\temp\node_modules\nan\nan.h(131): warning C4005: 'TYPE_CHECK': macro redefinition (compiling
source file ..\src\uwp.cc) [C:\Users\munyirik\Desktop\temp\node_modules\uwp\build\uwp.vcxproj]
C:\Program Files\NodejsUwp\Console\sdk\deps\chakrashim\include\v8.h(75): note: see previous definition of 'TYPE_CHECK
' (compiling source file ..\src\uwp.cc)
Creating library C:\Users\munyirik\Desktop\temp\node_modules\uwp\build\Release\uwp.lib and object C:\Users\munyiri
k\Desktop\temp\node_modules\uwp\build\Release\uwp.exp
Generating code
Finished generating code
uwp.vcxproj -> C:\Users\munyirik\Desktop\temp\node_modules\uwp\build\Release\\uwp.node Can you try installing another package (e.g. serialport) and see if you have the problem? |
The problem is he has a custom globally installed node-gyp, which takes precedence. The env variable would guarantee to use the correct node-gyp. If I am right, workaround is either define that env variable, or uninstall the global node-gyp. |
@munyirik I was talking about https://github.com/Microsoft/node-msft/blob/chnext-msi/tools/msvs/nodevars.bat#L10. Somehow the change got lost. |
Yeah, the chakra IoT branch (https://github.com/munyirik/node/blob/chakra-uwp/tools/msvs/nodevars.bat) is missing this commit - https://github.com/Microsoft/node-msft/commit/7ea206bcadab737d3e1d3d919bfb7a61e8b96570 |
@kunalspathak Do you know if current node-ChakraCore nightly has the same problem? Install a global node-gyp and that'll take precedence? BTW, @kunalspathak said node-gyp changes had been accepted. Maybe this won't be a problem with newer node-gyp release? |
The change I made only touched gyp so nothing under the tools directory. |
I'm planning to make another (node-chakra) release in a couple of weeks so I can include the change. |
But on the other hand maybe node-chakracore should be used (with NodeRT). |
Change in tools directory meant to always use local node-gyp. If newer node-gyp works (e.g. user acquires latest node-gyp and installs globally), then we don't need tools directory change. |
I am trying to follow the
Hello Blinky
tutorial sample, but have fallen at the first hurdle trying to install this. I have downloaded the node Chakra, opened that command line and then runnpm install uwp --target_arch=arm
(NB: I get the same result without the flagged argument).This is what I get:
Looking at the nodejs dists, it seems as though there is in fact no v7.0.0-pre8 release, only v7.0.0, v7.1.0, v7.2.0, v7.2.1 ... v7.5.0.
Can we fix this please?
The text was updated successfully, but these errors were encountered: