Skip to content

node --inspect: dev tools console not working #7891

Description

  • Version: 6.3.1
  • Platform: OS X 10.11.5
  • Subsystem:
  1. Start app with node --inspect;
setInterval(() => {
  const b = Math.random();
  console.log(b);
}, 1000);
  1. open dev tools by url from terminal;
  2. try execute anything in console.

screen shot 2016-07-27 at 11 57 04

I have suggest for input, but I can't execute code.

Activity

  1. added
    inspectorIssues and PRs related to the V8 inspector protocol.
    on Jul 27, 2016
  2. mscdex commented on Jul 27, 2016

    @mscdex
    Contributor
  3. claudiorodriguez commented on Jul 27, 2016

    @claudiorodriguez
    Contributor

    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

  4. ofrobots commented on Jul 27, 2016

    @ofrobots
    Contributor

    @zloylos I cannot reproduce this either. I have tried master, 6.3.0 and 6.3.1.
    /cc @eugeneo.

  5. nojvek commented on Jul 27, 2016

    @nojvek

    @zloylos, are other things like debugger and profiler working ?

  6. evanlucas commented on Jul 29, 2016

    @evanlucas
    Contributor

    @zloylos just curious, what do you have in /etc/hosts?

  7. WoodyWoodsta commented on Aug 8, 2016

    @WoodyWoodsta

    I'm having the same issue.

    • Version: 6.3.1
    • Chrome: 54.0.2816.0 dev (64-bit)
    • Platform: Ubuntu 16.04

    Inspecting the inspector with devtools shows a number of errors such as:
    image

    Changing localhost to 127.0.0.1 makes no difference.

    This appears to affect more than just the console, for instance, when I hit f11 to step into a function, the window goes fullscreen.

  8. eugeneo commented on Aug 8, 2016

    @eugeneo
    Contributor

    Error re Console.enable is expected (it will go away once #7988 lands).

    I'm looking into other failures.

    EDIT:ofrobots:fix link.

  9. eugeneo commented on Aug 23, 2016

    @eugeneo
    Contributor

    This should be fixed now.

  10. bnoordhuis commented on Aug 24, 2016

    @bnoordhuis
    Member

    Fixed by #7988.

  11. WoodyWoodsta commented on Sep 10, 2016

    @WoodyWoodsta

    I'm still having the original issue on the following:

    • Version: 6.5.0
    • Chrome: 54.0.2840.16 beta (64-bit)
    • Platform: Ubuntu 16.04
  12. WoodyWoodsta commented on Sep 10, 2016

    @WoodyWoodsta

    I'm getting the following errors when inspecting the inspector:

    image

  13. andrewjmead commented on Oct 27, 2016

    @andrewjmead

    +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.

  14. atif089 commented on Oct 30, 2016

    @atif089

    +1

    Tested on node latest as well as v6.9.1 ( Chrome 54.0.2840.71 m )

    I'm found that all works fine when I change debug URL query param from
    ws=localhost:9229/node to ws=127.0.0.1:9229/node

    @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 localhost to 127.0.0.1 through my node command?

  15. atif089 commented on Oct 30, 2016

    @atif089

    Hi @ofrobots @claudiorodriguez ,

    I made a small video to show the similar problem that I have been facing.

  16. nickolasclarke commented on Nov 14, 2016

    @nickolasclarke

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    inspectorIssues and PRs related to the V8 inspector protocol.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions