Josh Pike
Josh Pike
After updating zed preview... The child is the process I actually care about. Also can you take another look at the other debugger related issues I raised this week?
VSCode just shows one session... Node developers are generally high-level programmers and will easily get confused when seeing two processes at the same time, even if it becomes a tree....
This isn't what I'd call good UX. Those "Debug Server/Client" options are kind of useless on their own. I suggest when only one child process is fired up from the...
edit: I thought something else was broken, dw about it
closing issue as out of date. I'll re-paste my feedback: "I suggest when only one child process is fired up from the debugger, combine the debugger process and child process...
instead of trying to go all in with signals, just focus on adding changeDetectorRef.markForCheck() where needed
A nice win over VSCode on this one... nice!
in Editor.mjs, this.getInstanceState() returns an undefined object. That appears to be the root of the issue... the error should be better though. You probably cleared the store at the wrong...
It's awful UX to have a dev click a start button, when he was opening UI mode to commence the tests in the first place... when would someone want to...