Cannot debug Nodejs with node-inspector - Websocket_closed - javascript

I know that these are some similar / duplicate responses when searching for a solution to this. But the Node world seems to update so regularly that any answers I've found are refering to a much older version.
I'm currently running:
Node v6.9.1
Node Inspector v0.12.8
The error I get is as follows:
Detached from the target
Remote debuggng has been terminated with reason: websocket_closed
please re-attach to the new target

I had an identical issue. After digging around on some forums, I found that downgrading to Node v6.3.1. Here
So the next question was "How do I manage versions of node". Plenty of results show up with nvm. Stack Overflow has a post on it here.
None of the version managers for windows are kept up with. I found another one that is kept up to date (as of 1/1/17). I posted that answer here
Back to the original problem, with the nvm-windows installed:
nvm install v6.3.1 //I was running 6.9.1 - downgrade
The utility downgrades your npm version
Downloading npm version 3.10.3....complete
Installing npm v3.10.3
Then use it
nvm use 6.3.1
Note - I use a bunch of IDEs / Editors (depending on what I am doing). Editors such as Atom or WebStorm which have a Terminal / Command prompt embeded in it will need to be restarted AFTER you install nvm-windows in order to get access to the environment command "nvm".
Once you have node downgraded, the node-inspector worked find for me:
node-debug server.js

Maybe node with higher version(6.9.1) built in inspect, and node-inspect don't update longer..
solution:use node --inspect yourapp replace node-inspect & node --debug yourapp
It worked for me.
you can see Github issues Detached from the target, websocket_closed, cannot read property ref of undefined (NM[0] is undefined)

Related

Node vs Nodejs versions are different

I am starting to learn Nodejs and tried to install it.
Now, when I do node -v I get v4.4.4 and when I do nodejs -v, I get v0.10.45
which node gives /usr/local/bin/node, which nodejs gives /usr/bin/nodejs
I need v4.4.4. Because of those different results I am not sure to start.
What can I do?
I recommend installing NVM (node version manager). It makes dealing with multiple node version installations really nice. Digital Ocean has a good tutorial on doing that here:
https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-an-ubuntu-14-04-server
Once you've installed NVM you can likely remove your other node versions and all of your programs that use node will default to whatever version you set as the default with nvm.

Node Windows NPM not installing

I'm trying to simply install a stupid package in Node. I use the normal ol' command and it proceeds to tell me it can't find a file or directory (see image below). I've already updated and reinstalled npm, and still the same thing. I'm also running Windows 8. Any ideas, please?
Should I give up developing Node on a Windows machine?
Thanks!
Run npm init first and it will create the package.json file that it is looking for.

Uncaught Error: Module did not self-register

I try to use node-vlc with nw.js (v0.12.0-alpha2). When i launch my app without nw.js it works, but when i launch it with nw.js i got an error:
Uncaught Error: Module did not self-register.", source: /home/alexis/Bureau/dev/jukebox/node_modules/vlc/node_modules/ffi/node_modules/bindings/bindings.js (84)
I tried some commands with nw-gyp but it couldn't help me.
I am on Ubuntu 14, 64-bit.
If you've upgraded node then npm rebuild might fix this for you
For me:
rm -r node_modules then
npm install
I had a similar issue with another product and my fix was to change the version of node I was using. I was using 0.12.0 and changed back to 0.10.26.
Personally, I use NVM to handle node version changing. With NVM installed it's as simple as running
nvm use 0.10.26
Or setting the default version to 0.10.26
nvm alias default 0.10.26
Hopefully this helps you out - our issues came from different products but the solution may be the same.
I had similar problem.
/Users/user/NodeAddons/bridge/node_modules/bindings/bindings.js:83
Error: Module did not self-register.
In my case I was doing a C/C++ Add-on, and I had forgotten to export the add-on, in my main.cc was missing the code below:
void Init(v8::Handle<v8::Object> exports) {
NODE_SET_METHOD(exports, "method", method);
}
NODE_MODULE(method, Init);
Hope this helps others!
Thanks :)
I've add the same issue because I installed to modules as sudo...
Removing the node modules folder and reinstalling as normal user fixed it.
For me npm rebuild or npm update didn't work. I had to remove the node_modules folder and run npm install to install them again.
I once had this problem when creating a multi-file c++ addon. In my binding.gyp file I had:
"sources": ["src/*.cc", "src/*.h" ]
And my project contained several *.cc files. However, the NODE_MODULE() macro was called only on one file which imported the rest of the files. But node expects that it is called on the frist *.cc file listed in sources. So I had to change sources to explicitly add that file to the beginning
For me, running npm update worked
I was getting an internal error: Module did not self-register.
Deleted the node_modules folder
ran npm install
It worked just fine.
I had this error with Snappy. Was using Node 11. Checked Snappy's NPM page https://www.npmjs.com/package/snappy where they listed which versions of node they supported.
Deleting node_modules folder rm -rf node_modules and then reinstalling using the correct version of Node resolved it.
One of the versions they supported on Linux at the time of this writing was Node version 12.
nvm deactivate 11
nvm uninstall 11
nvm install 12
nvm use 12
Problem solved
Another cause of this problem: if you're using pm2, then after upgrading node you may need to reinstall pm2. Test whether pm2 is the issue by running your app
without pm2 node server.js
then with pm2: pm2 start server.js.
Proper way to update PM2 after updating Node.js
I had this same issue with 0.12 and io.js 1.3.0, reverting to Node.js 0.10 fixed the issue.
Rebuild your C++ add-ons.
Did you encounter something like this?
Module did not self-register: '…\node_modules\#u4\opencv4nodejs\build\Release\opencv4nodejs.node
It’s likely that you have just updated your Node.js. Once you updated your Node.js, you need to rebuild your C++ add-ons, Node.js packages written in C++.
Why
When you build Node.js’ C++ add-ons, they get compiled into require-able .node files and linked to the currently installed Node.js ABI library, which is not compatible with other versions of it. Your packages were built only compatible with the specific version of Node.js.
How
Firstly, try npm rebuild. If your C++-add-on-based packages have a build script, it’ll do. If it doesn’t, you need to manually build your C++ native add-on packages. Do again what you did when you were installing such packages. Refer to the building instructions in the packages’ documentations to rebuild them. Or try reinstalling (npm install) them.
I had the same problem. My script that was referencing a global reference script had an invalid reference. I took off that invalid reference and the error was gone. My error message had no indication of that particular invalid reference which made it harder to debug. But 'Uncaught Error: Module did not self-register' was the message I was getting.
This also happen in my other project. For some reason, it wouldn't recognize the reference path if one of the characters are uppercase. Even thought, the upper-casing was the correct spelling of the path.
I had this issue while setting up my Cypress project.
I found out the issue was caused because Cypress uses node from its bundle version by default (which was version 8.0 in my case) , whilst the package I wanted to use required the node version to be 10 or higher.
I did have node 12.0 installed on my machine but since cypress was not using that I had to add the line shown below in the settings file (cypress.json) to set the value for 'nodeVersion' to 'system', to tell cypress explicitly to use the node version installed on my machine.
Add this line to your settings file:
**"nodeVersion": "system"**

node Segmentation fault on version change

I'm trying to install node.js on a friend's computer. We had an old version (0.4.*), then installed n to update to a more recent version of node using n - node version manager
now instead of having an old version of node, we get
$ node -v
Segmentation fault
$ n --version
1.2.1
$ npm --version
Segmentation fault
When we type n the versions we installed show up but they are all greyed out. What's a Segmentation fault, why is it happening and how can we fix it?
Unless you're using something with binary dependencies (npm doesn't), segmentation fault means on of two things:
there is a bug in node.js core, and it should be reported
your node.js installation is broken
So you can solve this by reinstalling the most recent node.js version using a standard way from nodejs.org website. If it still segfaults (highly unlikely, but possible in some non-standard environments), report it to node.js core team.

node js npm package OSX fails

After reading many ( if not all :-| ) posts having similar problems, I still don't have a working local (or a "global") install of node.js's Mac OSX system tools. Showing global attempt here...
Their doc implies either an npm install or a build from source - but not npm THEN source. However, a test run seems to be requiring compiled file(s) that don't exist after the attempted install.
Details:
It's my understanding that npm should be sufficient, but when I do the recommended
sudo npm install -g osx
npm creates /usr/local/lib/node_modules and populates with
README.md osx.cc osx.js package.json wscript
Running (from anywhere) node theirSample.js, containing:
Var osx = require('osx');
// also tried full path as recommended in other answers
var osx = require('/usr/local/lib/node_modules/osx');
The error is the commonly seen "cannot find module". However, the specific error is:
Cannot find module './build/Release/osx'
Which stems from the above osx.js created in /usr/local/lib/node_modules
That file has the errant line:
var osx = require('./build/Release/osx');
That implies that I need the ./build/Release/osx dir, but npm did not create this under the modules dir. So does that mean I need to compile the source? If so, any pointers on set up please.
First of all, you don't need to install it globally, and second, this module is already 2 years old, and it was tested on Darwin 11.2.
It does not work with OS X "Mavericks" - just tested on my machine.
As a replacement, I would recommend to take a look at os build-in module, which provides basic operating-system related utility functions, and is OS-agnostic

Categories