Microsoft/vscode-chrome-debug

A Visual Studio Code extension to debug your Javascript code on targets that support the Chrome Debugging Protocol.

con-ssc

@con-ssc

only one debugger can be connected I think so either devtools or vscode

Assaf

@assaftenen

anyone got maybe aworking s;aunch.json configuration for debugging electron app?

Andre Weinand

@weinand

@assaftenen have you tried this: http://electron.atom.io/docs/tutorial/debugging-main-process-vscode/

Gunter Spranz

@gunters63

I am using VS Code 1.9.0, Debugger for Chrome 2.5.2 and Chrome 56.0.2924.87. I currently have the issue I can launch the debugger on a project in VS Code. Chrome comes up fine. But when I try to open the developer tools Chrome crashes immediately. It seemed to work last friday (there were some updates to VS Code and the debugger extension afaik). Anyone has similar experiences?

Gunter Spranz

@gunters63

Does this have something to do with Microsoft/vscode-chrome-debug#83 Strange that it worked a couple of times last friday.

Assaf

@assaftenen

@weinand yep, it does debug the app, but only under the scope of main page e.g main.js, or index.js.

Andre Weinand

@weinand

@assaftenen what other parts of an electron app do you want to debug?

Rob Lourens

@roblourens

@gunters63 That isn't expected to work unfortunately. Only one thing can debug Chrome at a time. I want to improve the experience there somehow, though

Gunter Spranz

@gunters63

Thanks, Rob

Teodorescu Stefan Eduard

@StefanEduard

hey how can i set up vs code chrome debugger for localfile

{
"version": "0.1.0",
"configurations": [
{
"name": "Launch localhost",
"type": "chrome",
"request": "launch",
"url": "http://localhost/mypage.html",
"webRoot": "${workspaceRoot}/app/files"
},
{
"name": "Launch index.html (disable sourcemaps)",
"type": "chrome",
"request": "launch",
"sourceMaps": false,
"file": "${workspaceRoot}/index.html"
},
]
}

i dont get how to set up "url": "http://localhost/mypage.html",
"webRoot": "${workspaceRoot}/app/files""

if that is the problem

Rob Lourens

@roblourens

@StefanEduard You need to start your own server, then provide the URL

Assaf

@assaftenen

At WebStorm by using F12 key, you can get small file scheme for quick file navigation. Does this behavior exists some how at VS Code?

Rob Lourens

@roblourens

Not sure what you mean by that - like what cmd+P does in vscode?

con-ssc

@con-ssc

I think he means the loaded scripts overview like in the dev tools

José Diaz Seng

@joseds

Hi, today debugging stopped working for me, I start Chrome as usual with --remote-debugging-port=9222 and did not change my launch configurations. Attach and launch configurations fail with error "Cannot connect to runtime process, timeout after 10000 ms - (reason: Got a response from the target app, but no target pages found)." I checked the log file, it says "Discovering targets via http://127.0.0.1:9222/json". Opening that URL shows an empty array... Should I see something there?

José Diaz Seng

@joseds

Never mind... After having updated Chrome to the current version it works again!

Tim Sandberg

@largeDachshund

has anyone had luck hooking this up to an Angular 2 project?

vasenju

@vasenju

Hello, Is it possible to inspect global and closure variables values with mouse hover? I can only view local variables that way.

amgadserry

@amgadserry

guys any luck debugging vuejs apps withthis plugin ?

symphony

@symphony2014

hello everyone, I had set the sourcemap:true, it seem like the vscode-chrome-debug doesn't work?

symphony

@symphony2014

Eugene Mikeshyn

@NogrTL

Hi,everyone.

Stupid question but could i open Opera instead of Chrome? Didn't find any instructions about it

Victor

@oldbasilbear

Hi folks.
Can anyone point me to a set of examples for using the sourceMapPathOverrides please - I am having trouble with a symbolic link

Victor Trevor

@VictorTrevor_twitter

I am having a hair-pulling time attempting to map a folder (containing code common to all projects) which sits outside of my main src folder.
I have this in launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "chrome",
            "request": "launch",
            "name": "SABRE1",
            "url": "http://localhost:4200/*",
            "webRoot": "/home/victor/src/sabre/sabre-hr",
            "sourceMapPathOverrides": {
                "webpack:///./*": "${webRoot}/*",
                "webpack:///./sabre-common/*": "/home/victor/src/sabre/sabre-common/*"
            },
            "runtimeExecutable": "/usr/bin/chromium-browser",
            "trace" : true,
            "userDataDir": "${workspaceRoot}/.vscode/chrome"
        },
        {
            "type": "chrome",
            "request": "attach",
            "name": "Attach to Chrome",
            "port": 9222,
            "webRoot": "${workspaceRoot}"
        }
    ]
}

I want to be able to add traps in the "common" files too - but I get the old "sourcemaps problem?" response.

bitbonk

@bitbonk

I created a simple new asp.net mvc core app on macOS using dotnet new mvc then I run it using launch.json in VS Code

I can debug C# just fine but I cannot debug javascript. When I put a breakpoint in site.js it stays gray and it says

no symbols have been loaded

Any idea what could cause this? Should I be able to debug javascript on macOS in VS Code?

bitbonk

@bitbonk

these are my launch settings:

"version": "0.2.0",
   "configurations": [
        {
            "name": ".NET Core Launch (web)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceRoot}/bin/Debug/netcoreapp1.1/Ludewig.PhotoSite.dll",
            "args": [],
            "cwd": "${workspaceRoot}",
            "stopAtEntry": false,
            "internalConsoleOptions": "openOnSessionStart",
            "launchBrowser": {
                "enabled": true,
                "args": "${auto-detect-url}",
                "windows": {
                    "command": "cmd.exe",
                    "args": "/C start ${auto-detect-url}"
                },
                "osx": {
                    "command": "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
                },
                "linux": {
                    "command": "xdg-open"
                }
            },
            "env": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "sourceFileMap": {
                "/Views": "${workspaceRoot}/Views"
            }
        },

I need to find a way to attach both c# and js

Andre Weinand

@weinand

@bitbonk Your launch configuration is for "coreclr" (C#). You cannot use it for debugging JavaScript. You'll have to add another launch configuration for JavaScript.

Aapiz

@Aapiz

I'am not able to connect to localhost in visual studio code

Help me with this

Aapiz

@Aapiz

Anyone there????

Anurag Sharma

@RedHope

@Aapiz You haven't really provided much information with which anyone here can help you.

What are your launch.json settings? What error are you getting ?

Jeffrey Layanto

@layanto

Has anyone got vscode debugging working with vuejs, vue-loader and webpac? Debugging in Chrome Dev tool works but in vscode if I set a breakpoint, it either gets set on the wrong line or doesn't get set at all. Not sure if issue with chrome debug extension, Vue loader, webpac or my config.

Rob Lourens

@roblourens

@layanto It's a pain. See Microsoft/vscode-chrome-debug#430 for some details

Jeffrey Layanto

@layanto

Thanks. Found that issue after posting in Gitter.

Dylson

@n370

I've been getting the following message "Breakpoint ignored because generated code not found (source map problem?)." while trying to debug Karma tests using this tool. Anyone here has gone or is going through this same situation? Any comment is appreciated.

Dylson

@n370

Solved. Forgot to configure the webRoot property.

Basheer A Radman

@ba2015sheer_twitter

Thank you @alshamiri2

Andrew

@CanadianEngineer

Hey, is anyone else having issues with the command --auto-open-devtools-for-tabs? I've setup my launch.json to start the chrome debugger, but with --auto-open-devtools-for-tabs added, chrome starts, but the process is never hooked by VS Code

Jonas Kemper

@jk21

hello, i have a source map problem. my config is following:

"configurations": [
    {
        "type": "chrome",
        "request": "launch",
        "name": "Launch Chrome against localhost",
        "url": "http://localhost:8081",
        "webRoot": "${workspaceRoot}",
        "trace": true
    },

when i run .scripts i have following outputs:

› webpack-internal:///562

- webpack:///src/components/Fields/Content.jsx?e3b2 (src/components/Fields/Content.jsx)

but no breakpoint is working

Jonas Kemper

@jk21

okay got it to work with the suggestions in Microsoft/vscode-chrome-debug#454 and overwriting the source-map path

Where communities thrive

People

Repo info

Activity