hello. sometimes when debugging (with source folder added to workspace in Chrome devtools) every single .js file loads in devtools when I start a debugging session. Most of the time they don't but when they do they load up as they are used in the app. I can't think of any steps to replicate other than starting a new vs-chrome-debug session - and like I say it doesn't always happen. Sorry I don't have better info but I thought you might want to know.
@nfgallimore are you, by chance, using WSLv2? If you are, that could be related.
@clshortfuse No sir
Any updates on this issue?
Anyone run into performance issues with the Edge Beta? I am seeing a 5-10 second lag between event triggered in Edge and breakpoint in VSCode?
What does this have to do with Chrome?
Are you debugging in Edge?
New edge is chromium
Huh interesting, cool.
the extension mostly just works
I can't get it to work at all for me now and have been waiting for a fix forever lol
need to use the Beta version
Where do you get that? Are you building it from the repo?
It randomly started working again
is it possible to clear the debug console when the browser refresh? I am running an angular development server that reloads when it detects changes, I'd like to start with a fresh debug console each time
It should clear already no?
Hi. Anyone using serverReadyAction with "action": "debugWithChrome"? The debugging Chrome is not closed as stop debug. Is it possible to close Chrome at same time as debug stops?
@AlphaKhan_twitter same here... it resulted in Chrome "Inspectable Pages" instead of our index.html (Hello world web) How to fix? Should we need to install Nginx?
Anyone having problems with debugger hanging on async calls when you set a breakpoint on it?
I would need help setting up chrome debugger in attach mode
I know it has worked in the past. I'm using it in the Debug Console after I have launched a debug.
Other JS commands work fine.
Turns out I had the preview js debugger. Removing that fixed this.
i can't F5 lanuch the debugger.....WTF ?????????????????? SUDDENLY!!
@chiuan I have the same problem. How to
I can't seem to get the debugger in VSCode working anymore, since i upgraded to WDIO v6. It seems to start and then immediately stop. And then when I run other npm commands in the terminal. it seems to still be listening I get something like
revert to version 4.12.8
it works for me
Hello! I was running the extension with React + Ruby on rails. I had two debug configurations: one for rails and another for React. They both were working. I used to lunch first Rails debugger before lunching the react one. I don't know why, but the React configuration stopped working. Can someone help me? I am using react with typescript
Hi Guys. Is there an option to pass more parameters to launch.json serverReadyAction: "debugWithChrome" like sourceMapPathOverrides or reference other launch configuration?
I'm facing problems to get my html code live on server