Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Nick Gallimore
    I have the same launch settings as @MattHubbell and am getting the same error. Has there been any fix for this? https://files.gitter.im/Microsoft/vscode-chrome-debug/6rf0/debugger_error.jpg
    Carlos Lopez
    @nfgallimore are you, by chance, using WSLv2? If you are, that could be related.
    Nick Gallimore
    @clshortfuse No sir
    Nick Gallimore
    Any updates on this issue?
    Zach Whitesel
    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?
    Nick Gallimore
    What does this have to do with Chrome?
    Are you debugging in Edge?
    Zach Whitesel
    New edge is chromium
    Nick Gallimore
    Huh interesting, cool.
    Zach Whitesel
    the extension mostly just works
    Nick Gallimore
    I can't get it to work at all for me now and have been waiting for a fix forever lol
    Zach Whitesel
    need to use the Beta version
    Nick Gallimore
    Where do you get that? Are you building it from the repo?
    Nick Gallimore
    It randomly started working again
    Andrea D'Amore
    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
    Nick Gallimore
    It should clear already no?
    Shawn Roberts
    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?
    Alpha Khan
    HELP: using VSCODE to debug a javascript file on OSX -- when i run the debugger chrome fires up for localhost:8080 but cant connect --- How to fix
    @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?
    Shawn Roberts
    Srđan Međo
    Hello everyone
    I would need help setting up chrome debugger in attach mode
          "type": "chrome",
          "request": "attach",
          "port": 9222,
          "name": "Attach to Chrome",
          "url": "http://localhost:3001",
          "webRoot": "${workspaceFolder}"
    this is my config but it times out
    any ideas what am I not setting up corretly ?
    chrome is started in remote debug mode with that port
    Hello. Not sure if this is the right place to ask - but .scripts isn't working for me.
    Uncaught SyntaxError: Unexpected token '.'
    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
    Míla Kuchta
    Hi Guys. Is there an option to pass more parameters to launch.json serverReadyAction: "debugWithChrome" like sourceMapPathOverrides or reference other launch configuration?
    Neelmani Shukla
    Hi Developers,
    I'm facing problems to get my html code live on server
    from VScode
    Hi. is there someone who could help with blazor-webassembly-chrome-extension related issues