-
Notifications
You must be signed in to change notification settings - Fork 13
Description
I recently started using the editor widget in an application based on blessed. Now I noticed that I can't debug properly anymore - as soon as the debugger is attached, the screen is plastered with messages like this (strangely enough, debugging seems to work fine while this happens).
Starting inspector on 127.0.0.1:9229 failed: address already in use
The port varies - if I start the debugger from VS Code, it assigns a new random port every time, and the message remains the same with the exception of the port. Using the Node debugger in Chrome shows the same problem though, this is not a VS Code issue.
Tests showed me that my application debugs just fine if I replace the line where I call new Editor(...) with blessed.box(...). I may go and read source code to figure out what it is that the editor widget does that breaks debugging - meanwhile, any ideas from those who know the project?