Repository navigation
node --inspect: dev tools console not working #7891
Description
- Version: 6.3.1
- Platform: OS X 10.11.5
- Subsystem:
- Start app with
node --inspect;
setInterval(() => {
const b = Math.random();
console.log(b);
}, 1000);- open dev tools by url from terminal;
- try execute anything in console.
I have suggest for input, but I can't execute code.
Activity
mscdex commentedon Jul 27, 2016
/cc @ofrobots
claudiorodriguez commentedon Jul 27, 2016
I am following the steps, and the console in the inspector works - I can even do
console.log('a')and that (a) shows up in the cli running the node process (which is outputting a random number on interval).I have node v6.3.1 and OS X 10.11.3
ofrobots commentedon Jul 27, 2016
@zloylos I cannot reproduce this either. I have tried
master, 6.3.0 and 6.3.1./cc @eugeneo.
nojvek commentedon Jul 27, 2016
@zloylos, are other things like debugger and profiler working ?
evanlucas commentedon Jul 29, 2016
@zloylos just curious, what do you have in
/etc/hosts?WoodyWoodsta commentedon Aug 8, 2016
I'm having the same issue.
Inspecting the inspector with devtools shows a number of errors such as:
Changing localhost to 127.0.0.1 makes no difference.
This appears to affect more than just the console, for instance, when I hit
f11to step into a function, the window goes fullscreen.eugeneo commentedon Aug 8, 2016
Error re Console.enable is expected (it will go away once #7988 lands).
I'm looking into other failures.
EDIT:ofrobots:fix link.
eugeneo commentedon Aug 23, 2016
This should be fixed now.
bnoordhuis commentedon Aug 24, 2016
Fixed by #7988.
WoodyWoodsta commentedon Sep 10, 2016
I'm still having the original issue on the following:
WoodyWoodsta commentedon Sep 10, 2016
I'm getting the following errors when inspecting the inspector:
andrewjmead commentedon Oct 27, 2016
+1
Still seeing this issue in Node v7.0.0 and Chrome 54.0.2840.71 (64-bit). At this point it seems more likely to be an issue with the Chrome Dev Tools but I wasn't able to find a similar bug over there.
atif089 commentedon Oct 30, 2016
+1
Tested on node
latestas well asv6.9.1 ( Chrome 54.0.2840.71 m )@zloylos answer worked for me but for that, I also need to open the link in Incognito Mode.
Is it possible to change the web socket host from
localhostto127.0.0.1through my node command?atif089 commentedon Oct 30, 2016
Hi @ofrobots @claudiorodriguez ,
I made a small video to show the similar problem that I have been facing.
nickolasclarke commentedon Nov 14, 2016
Also seeing this on Node 6.9.1 on Chrome 54.0.2840.87 m (64-bit). However, my node is being run from WSL (Windows Subsystem for Linux). I've not yet tested on node installed directly on windows. However, following @zloylos also seemed to resolve the issue for me.