node-pre-gyp install --fallback-to-build #7
Comments
|
How about this issue? Is this helpful for you? |
|
Didn't solve my problem. I saw node-gyp required VS2012, so I installed it and set the npm's config related, but still it doesn't work. Do you think there is any relation to npm's version 2.1.16? |
|
I re-install nodejs and python to 32-bit version, and now it works. It seems like there some issues regarding 64-bit |
|
I'm facing the same trouble. @sparkGitHub could you share the steps you did to solve it? |
|
I added some fixes to v8-profiler and v8-debug. Also I added prebuild binaries for Linux and OSX. |
|
I am having this issue as well I appear to be having a similar issue...any udpates? |
|
Same issue here pm ERR! Darwin 14.5.0 npm ERR! [email protected] install: npm ERR! Please include the following file with any support request: |
|
Same issue here |
|
Same issue with [email protected] |
|
Same problem, but running on Debian. Here's the actual erroring out leading to the failure message : CXX(target) Release/obj.target/debug/src/debug.o |
|
I'm seeing the same thing when I try to build the default Yeoman angular-fullstack. node-pre-gyp 0.6.10, Node 4.1.0, OS X 10.10.5 |
|
I also am seeing this issue when I try to run npm install using Yeoman angular-fullstack Errors start at:
CXX(target) Release/obj.target/debug/src/debug.o then... 1 warning and 10 errors generated. and end with npm ERR! Darwin 14.5.0 npm ERR! [email protected] install: |
|
The problem is in grunt-node-inspector, which was linked to outdated node-inspector version. |
|
Same problem for me, solved by npm install -g grunt-node-inspector, which installs the latest version (0.3.0) which doesn't seems to have the problem. |
|
I am getting the same "Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'." error. I have tried rolling npm back to v2, that did not fix it. I have tried the suggestion above 'npm install -g grunt-node-inspector' but that did not fix the issue. |
|
@hanssl , Maybe |
|
I have tried ‘npm cache clean’ with ‘bower cache clean’ many times. Problem persists. I have attached my npm log.
|
|
Does this have any sense: "opened this issue on Dec 25, 2014"???? I leave Windows hoping to avoid this issues, after spending ages on node-gyp nonsenses. So now I need to spend week to make PR to grunt-node-inspector and hope somebody will accept in order to use it until next bug appear? |
|
npm ERR! Linux 3.13.0-57-generic npm ERR! [email protected] install: Same issue here, I'm running ubuntu. |
|
Rollback to node 4.2.2 solved problems for me on Ubuntu 14.04. |
|
I was on node 5, rolled back to node 4.2.2 but still the same error. I'm on OSx 10.11. In my case the issue happens with angular-fullstack as well or rather Any new insights? |
|
I was experiencing this same issue. Changing in the version for grunt-node-inspector to prepend a ">=" instead of a "~" got this to work for me. |
|
@russfrisch worked for me as well, thx |
|
@russfrisch worked for me as well on Node 0.12.7. Thank you. |
|
I encountered the same problem when trying to install meanjs with [email protected] and [email protected]. Going into the package.json (in the cloned meanjs repo) and changing
to
did the trick. Thanks @russfrisch ! |
|
Thanks @russfrisch |
|
You can also update the package.json to |
|
+1 |
also added grunt-simple-watch node-inspector/v8-debug#7
|
Can some one tell me how can i change the globaly installed grunt-node-inspector from this version 3.6.0 to "grunt-node-inspector": ">=0.2.0" ? |
|
can someone help me in removing these errors ? I tried npm cache clean but it didn't work for me. Please find the attachment. |
|
Using |
|
thanks@rattrayalex i tried to upgrade node gyp using npm install -g node-gyp and it's working for me |
|
Recommend avoiding node-inspector altogether until this is fixed. Here's the cause of v8-debug failing to install:
Unfortunately, I don't have the time/knowledge to update This also applies to the following open issue: #26, #28, and #30. |
|
I was finally able to successfully install node-inspector by switching to Node v6.5.0 If you using n https://github.com/tj/n you can do: |
|
As per @singsai said, downgrade the nodejs to version 6.10.0 and install npm install -g n. We did below instead and run npm install node-inspector works well. |
|
gyp support python2.X，not python3. so if you use python3, change to python 2.X, ( 2.X >= 2.5 ), and set the enviroment path for python 2.X |
|
I was resolved my problem by install package in native console, install via ssh terminal was not wokrked. |
|
Downgrading node to |
|
Any Other Solution ?? I Want to install for Node v8.x |
|
thanks @russfrisch +1 its work for me also |
|
After checking the FAQ of node-pre-gyp, I might need to install the C++ runtime. I am installing it now and give feedback here tomorrow. However, for Node C++ modules on Windows that depend on external shared libraries, you'll need to understand whether those libraries were linked with /MD or /MT. If the external DLL was linked with /MD then you'll likely need to also link your Node C++ addon using /MD and you'll need to ensure that your users have the right C++ runtime installed for your addon binary to work. For example, if you compiled your binary with Visual Studio 2013 then your users would need This "C++ Redistributable". |
|
I am not sure why the proxy is invalid, I already configured the proxy as https://stackoverflow.com/questions/40171953/node-npm-proxy-authentication-how-do-i-configure-it. It's just a warning. Anyone knows something about this? @russfrisch
|
Someone has submit an issue in node-inspector already |
|
@antharamshivakumar Is the problem solved? My computer is the macmini。I need your help。thanks a lot |
|
@zhaoyongjiang No, I gave up. And I find the following message for node-inspector
I decide to use the built-in debugger in Node.js . |
|
@russfrisch +1 worked for me |
|
@chucklu thanks a lot |
|
anybody encountering the same in the latest ubuntu ? i changed to ">=" as suggested here. But it failed. |
|
I'm on OpenSUSE and for me, nothing here is working. I'm having the same error and the same with Linux mint, anyone knows another way to make it works? |
and others
I am getting below error while installing v8-debug, any ideas?
1035 info install [email protected]
1036 verbose unsafe-perm in lifecycle true
1037 info [email protected] Failed to exec install script
1038 verbose unlock done using C:\Users\Nadav\AppData\Roaming\npm-cache_locks\v8-debug-6a84c2f0ebeb5635.lock for C:\Program Files\nodejs\node_modules\v8-debug
1039 verbose stack Error: [email protected] install:
node-pre-gyp install --fallback-to-build1039 verbose stack Exit status 1
1039 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:212:16)
1039 verbose stack at EventEmitter.emit (events.js:98:17)
1039 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:14:12)
1039 verbose stack at ChildProcess.emit (events.js:98:17)
1039 verbose stack at maybeClose (child_process.js:766:16)
1039 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:833:5)
1040 verbose pkgid [email protected]
1041 verbose cwd C:\Program Files\nodejs
1042 error Windows_NT 6.2.9200
1043 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "v8-debug"
1044 error node v0.10.34
1045 error npm v2.1.16
1046 error code ELIFECYCLE
1047 error [email protected] install:
node-pre-gyp install --fallback-to-build1047 error Exit status 1
1048 error Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'.
1048 error This is most likely a problem with the v8-debug package,
1048 error not with npm itself.
1048 error Tell the author that this fails on your system:
1048 error node-pre-gyp install --fallback-to-build
1048 error You can get their info via:
1048 error npm owner ls v8-debug
1048 error There is likely additional logging output above.
1049 verbose exit [ 1, true ]
1050 verbose unbuild node_modules\v8-debug
The text was updated successfully, but these errors were encountered: