-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error, Node.js: unable to find page with socket #29
Comments
the same problem |
+1 |
+1 here. On a Mac, using the Remote Process mode, I set it to |
+1 |
+1 I've edited the node-launcher-files as suggested here https://github.com/xatom-plugins/xatom-debug-nodejs/issues/4#issuecomment-309239036 Now the debugger starts bug it seems Atom cannot attach the debugger process (unable to find page with socket) But when I manually set the port displayed in the command line window to the options I get it working. It seems like the port set in the options is not forwarded to the command line tool of node-launcher |
I had node 6.10 and same issue, then I update node to 8.5 and it works now. |
+1, in Ubuntu 16.04 and Windows 7. |
Same problem, windows 10 x64, node v6.11.2, Atom v1.21.1 x64. |
Anyone knows how to fix this issue in xatom chrome debug? |
When I tried to use this debugger it gave me the title message in the title.
I configured node.js as
Run Type: current file
Binary Path: C:\Program Files\nodejs\node.exe
Port: I tried 5858, 8000, 80. Nothing worked.
launchArguments: mysqlTest.js
How do I resolve this error?
The text was updated successfully, but these errors were encountered: