Skip to content
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

enter key in console and "add watch expression" performs line-break not execute #903

NilsFrkal opened this issue Aug 11, 2016 · 21 comments


Copy link

@NilsFrkal NilsFrkal commented Aug 11, 2016

When entering commands/variables in the console (both break-point and non-break-point scenarios) or when specifying a variable under "add watch expression" the "enter" key does not execute the command/variable, but does a line-break instead. I could not find any other way to actually execute the command in the console. How can this behavior be changed or is this a bug? Thank you very much.

node-inspector version 0.12.8
nodejs 5.12.0
chrome Version 54.0.2824.0 dev-m (64-bit)

Copy link

@corsen2000 corsen2000 commented Sep 22, 2016

Having the same issue. Any advice?

Copy link

@NilsFrkal NilsFrkal commented Sep 22, 2016

I did not work out how to fix it. Interestingly however, I had this issue on both my desktop and my laptop. Because of an issue I had to revert back to an older backup for my desktop (this backup did not have node inspector and chrome installed). After re-installing above sws the issue did not occur anymore whilst on the laptop it still exists. If you have time try de-installing both chrome and node-inspector and re-install.

Copy link

@ac9 ac9 commented Oct 18, 2016

I ran into this same issue. I could not fix it by reinstalling chrome and node-inspector.
I could only fix it by rolling back to Version 51.0.2704.106 (64-bit) then disabling auto update to prevent the overwrite.

node-inspector version 0.12.8
nodejs v4.2.2
Chrome 54.0.2840.59 (64-bit)
OS X El Capitan Version 10.11.6

Copy link

@newpost newpost commented Oct 22, 2016

i have same issue

Copy link

@oleksiipysanko oleksiipysanko commented Oct 25, 2016

Same issue here

OS: macOS Sierra 10.12.1
Chrome: Version 54.0.2840.71 (64-bit)
node-inpector: 0.12.8

Note: same issue in watch - enter starts a new line

Copy link

@ejhayes ejhayes commented Oct 26, 2016

It looks like this issue might be related to a Chrome update in 54.0.2840.71. I rolled back to 51.0.2704.106 and this issue disappeared. I couldn't find a copy of Chrome version 53.0.2785.101, but I suspect that it would also work.

  • Node: 4.2.6
  • OS: El Cap 10.11.3
  • Chrome: 54.0.2840.71 (previous version 51.0.2704.106 works)
Copy link

@oleksiipysanko oleksiipysanko commented Oct 26, 2016

Confirmed, working fine on 51.0.2704.84 (64-bit) Chrome

Copy link

@Mido22 Mido22 commented Oct 28, 2016

people, I am kinda struck, no official option to downgrade chrome in windows, (and I don't trust 3rd party stuff), so would request a higher priority to solving this bug.

Copy link

@emimull emimull commented Oct 29, 2016

same here. on windows. stuck.

Copy link

@Mido22 Mido22 commented Oct 31, 2016

good news, found a temporary work around, retrieved chromium 53.0.2785.34, so it is kinda official/ trust-able, you can find how to retrieve older chromium versions here

Bad news, tried chrome canary v56, the issue persists in that too.

Copy link

@iamfrontender iamfrontender commented Nov 1, 2016

Look for workaround at #942

Copy link

@sebastianconcept sebastianconcept commented Nov 24, 2016

Having this issue on OS X
I'm using this one that seems to be okay

Copy link

@devmi devmi commented Nov 30, 2016

If you would prefer to change node-inspector code instead of downgrading Chrome, here is a nice fix (tested on Chrome 54.0.02840.98, Mac OS X, node-inspector v0.12.8)

Copy link

@a7madgamal a7madgamal commented Dec 22, 2016

any updates on this issue? it's super critical!

Copy link

@neutrino84 neutrino84 commented Feb 4, 2017

the edit in #951 works perfectly for me, i'm pretty sure that pull request should be accepted, it's a simple change, how can it be failing a test???

Copy link

@Lexicality Lexicality commented Mar 8, 2017

Looks like the test just timed out. Anyone with write access should be able to re-run it.

abernix added a commit to meteor/docs that referenced this issue Mar 9, 2017
Due to a bug in `node-inspector`, pushing "Enter" after a command on the Node Inspector Console will not successfully send the command to the server.


This helpful tip can be reverted if/when node-inspector/node-inspector#955 lands.
Copy link

@a7madgamal a7madgamal commented Apr 5, 2017

can someone please re-run the test?

Copy link

@kubakoz kubakoz commented Jul 25, 2017

If anyone is still having this problem, I just created a solution in the form of a chrome extension.

Thanks to some insights I've read online about the nature of this issue, I made a simple "hack" that will resolve the problem.

Let me know if it works for you!

Copy link

@hustxiaoc hustxiaoc commented Jul 26, 2017

This issue had been solved in #1006

Copy link

@szebenyib szebenyib commented Oct 17, 2017

It still did not work for me, but @kubakoz 's plugin has helped! Many thanks 👍

Copy link

@linegel linegel commented Apr 13, 2018

At the end, is this issue solved or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.