Sounds like Chromium Remote Configuration is just what I was looking for. I'll check that out later, when I have a chance. Thanks.
-
-
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 -
-
-
Replying to @ATGardner
Thanks! The problem is because of the slashes in paths on Windows. Working on a fix.
1 reply 0 retweets 1 like -
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 -
Replying to @ATGardner @WebStormIDE
similar to https://youtrack.jetbrains.com/issue/WEB-21358 I have an easy repro at https://github.com/ATGardner/remote-debug … - should I open a bug?
1 reply 0 retweets 0 likes
Thanks for a repo. We'll check as part of that issue.
-
-
Replying to @WebStormIDE @ATGardner
Hi! Can you please try to use --inspect-brk instead of --inspect?
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
I just did. It's actually worse. The "working" example works just fine, but the "failure" example breaks at the first line of every js file>
1 reply 0 retweets 0 likes - 5 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.