question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chrome tab not closing properly when using Nodemon

See original GitHub issue

I have an issue where restarting my server through Nodemon does not close the tab, but instead renders this error message:

screenshot 2016-12-17 21 19 28

After looking through the source code I think I’ve isolated the problem to here. The catch for the HTTP request does not consider a valid case where the debug server is not down, but the ID of the debugger websocket changes.

A proposed solution would be to store the unique identifier for each devtools session, and check if that identifier is in the returned JSON from the localhost debug server. Requests coulda also be minimized by making the request only once and filtering $scope.devToolsSessions according to the returned identifiers.

I’d be willing to PR this in the next couple days with your OK @june07

Edit: Initial conversation about this issue can be found here.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:1
  • Comments:10 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
june07commented, Dec 26, 2016

No worries. Glad to help. And thank you for the positive feedback! If it’s not too much trouble, a review and/or rating at the Web Store would help out greatly.

On Dec 25, 2016 11:31 PM, “Darryl Dexter” notifications@github.com wrote:

Sorry, commented before I worked it out. Needed to update chrome apparently… Thx, awesome plugin!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/june07/NIM/issues/1#issuecomment-269176827, or mute the thread https://github.com/notifications/unsubscribe-auth/AK099lT6OEK2n48hjRPQEp_l-l9uecPcks5rL21WgaJpZM4LQFWn .

1reaction
june07commented, Jan 14, 2017

Are you using the current version? Any additional information you can provide will be helpful in figuring out what is going on. I’m sure you have already but in case not, please read through the entire thread as some information may be helpful.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How does Nodemon go with the newest node feature ... - GitHub
How does Nodemon go with the newest node feature "node --inspect" #903 ... Chrome tab not closing properly when using Nodemon june07/NiM#1.
Read more >
Open and close tabs in Chrome browser - Google Support
Open Chrome browser. Choose an option: Next to the last tab on the right, click New tab "" . Use a keyboard shortcut:...
Read more >
Can I get node --inspect to open Chrome automatically
Currently there is an issue with debug() not printing text in chrome inspector, However for the moment at least the text is visible...
Read more >
332334 - Close X tab button doesn't work - chromium - Monorail
I have exactly the same problem with the X to close a tab not working while Ctrl-W still works properly. The problem has...
Read more >
NIM (Nod Inspector Manager)
NIM manages the Chrome DevTools window/tab life-cycle leaving you with more ability ... Chrome tab not closing properly when using Nodemon #1 -...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found