New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install on Windows [Node 0.12] #559
Comments
I have problems to simon's above. I was using node 10.33 and node-inspector 0.83 and decided (as is often the case) to update to the latest and (greatest?). |
install python 2.7.9 |
I changed my node version back to 0.10.36, then node-inspector can be installed correctly. Maybe we can focus on the changes made between node 0.11.9 and node 0.10.36 |
Why 0.11.9? This is unstable version. We can't support all unstable subversions. From 0.11.9 to 0.11.13 debugging API was changed dramatically. |
I just updated from node v0.10.36 to v0.12.0 on Windows 7 x64 and was unable to install node-inspector (v0.8.3) via npm. I am using npm v2.5.1. I tried installing python-2.7.9 per the suggestion above and this solved the installation issue (python v3.4.2 did not solve the issue, you must install 2.7.9). Although the installation appears to be successful, debugging doesn't appear to be functioning properly. When starting node-inspector, I see the following console message in Chrome browser:
The debugger then steps into node.js' function _tickCallback() {...} and debugging hangs. |
same problem here :( |
same problem described by @cookch10 |
Is the problem still present on the latest Node 0.12 version using the Node Inspector version from github master branch? |
Updating to the latest version of iojs worked for me, the culprit was when building v8-profiler. I still got errors, but some optional dependencies fail to build. |
@simonvizzini I'm getting similar errors on my machine.
Regardless the errors node-inspector seems to be working fine.
|
For me node-inspector with node 0.12.7 seems to work fine now on Windows, I also still got some errors while installing, but apparently nothing critical (didn't pay too much attention and haven't saved any logs), So far node-inspector seems to work fine! Really awesome tool :) I don't have the other problems mentioned in the issue. Not sure if this issue can be closed, or if others are still unable to install on Windows? |
.. so... ignore the original version of this comment completely. The solution to installing this on windows -- at least for me -- is the same as many packages that have trouble with windows:
Apparently one of the optional dependencies kills the install script, ignoring them works swimmingly. |
@jamietre: passing The error included this:
and
Hey @node-inspector, what are the actual prerequisites for Windows? That should be listed in the README. |
@dandv I was getting the same error. Installing VS should fix that one. In addition I had to install node-gyp, python and a C++ compiler (I didn't have one.) Following post from a fellow user described the steps to install all the necessary requisites. Hope it helps.
|
Hello,
I'm trying to install node-inspector since an hour on my Win 8.1 x64 machine, but I'm getting all sorts of errors when doing
npm install node-inspector
. Every time I fix an error, a new one appears. I didn't see any special steps for Windows installations, like external dependencies in the documentation so I thought it should be pretty much a single npm command.I should mention that I'm new to the node and npm world, so it's possible that I'm doing something completely wrong
I'm currently using node version
0.11.9
and I'll try to explain every issue I had so far trying to install node-inspector, because I think it's not just a node-inspector problem and I think you guys could clarify the one or other thing. (I was able to fix most issues on my own but now I'm stuck).First issue:
Installation failed because the dependent
semver
package could not be installed because themake
command could not be found. Huh? Ok I triednpm install semver
to see if that works but it still complained about missing make. I then installed make for Windows, added it to my PATH variable and tried again. But still no luck, this time make was giving me some cryptical error output. At this point I remembered that I had troubles installing gulp at work a couple of days ago, and the solution to that problem kinda baffled me. It also solved my issue here! The thing is thatnode 0.11.9
ships withnpm 1.3.14
, but the current version of npm is2.5.1
! Even the 1.x version is at1.4.26
, so why is such an old version shipped with node? Once I updated npm to 2.5.1 I was able to install gulp, as well as semver without issues. This totally makes no sense.Second issue:
Now that semver was installing fine, I tried to install node-inspector again. But this time node-gyp was complaining: Command 'python' not found... Well ok then, I installed latest Python 3.x, tried again, and this time I got: Error: Python 3.x is not supported... you got to be kidding me. I checked the node-gyp homepage and there is written that I need some old 2.x version. And when running on Windows Visual Studio 2012/2013 is additionally required to run node-gyp. Luckily I already have VS 2013 installed, otherwise I'd probably have given up by now. Maybe it should be mentioned somewhere that python 2.x and VS 2012/2013 is required in order to install node-inspector on Windows.
Third issue:
Okay so I installed python 2.x and tried once again. This time no more python errors, but instead a wall of red text, which seem to be C++ compiler errors. That's where I'm stuck now because I have no clue what to do.
I redirected console output to a file and it's 300kb of text, the npm-debug.log is 845kb, but I guess the last few lines are the most important ones so I will post them here. Let me know if the debug.log is required and I will upload it somewhere.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: