Is there a way to use node --inspect, and then remote debug it using @WebStormIDE ? Or do I have to use @ChromeDevTools for it?
-
-
Replying to @ATGardner @ChromeDevTools
WebStorm is using --inspect in Node.js debug configuration by default now for newer node versions.
1 reply 0 retweets 2 likes -
Replying to @WebStormIDE @ChromeDevTools
so when I run "node --inspect index.js" (using node 8.1.3), how can I connect webstorm debugger to it? Node.js Remote Debug doesn't work.
1 reply 1 retweet 1 like -
Replying to @ATGardner @ChromeDevTools
If you run the index.js using Node.js debug configuration it will run with --inspect and connect automatically
4 replies 0 retweets 2 likes -
Replying to @WebStormIDE @ChromeDevTools
Sounds like Chromium Remote Configuration is just what I was looking for. I'll check that out later, when I have a chance. Thanks.
1 reply 0 retweets 1 like -
I created a Chromium Remote config, and if I run with --inspect-brk, I can debug the app's start. But breakpoints in WebStorm don't work.
1 reply 0 retweets 2 likes -
Replying to @ATGardner @ChromeDevTools
We'll investigate and let you know. Sorry for the inconvenience!
1 reply 0 retweets 1 like -
Replying to @WebStormIDE @ChromeDevTools
Thanks for your Swift response. I'm running the latest 2017.2 beta currently.
1 reply 0 retweets 1 like -
-
Thanks! The problem is because of the slashes in paths on Windows. Working on a fix.
-
-
Replying to @WebStormIDE
Just installed the new RC, and it works like a charm. Thanks for a quick fix!
1 reply 0 retweets 2 likes -
Replying to @ATGardner @WebStormIDE
Still a bit buggy - when js relative path does not match the end of the path inside the docker conatiner, breakpoints hit in remote files
1 reply 0 retweets 0 likes - 9 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.