Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    con-ssc
    @con-ssc
    Doesn't persist changes in js on reload though :(
    Only working way seems to be fiddler but then I have no debugging in vscode
    con-ssc
    @con-ssc
    Would it be possible to attach the vscode chrome debugger to an open chrome devtools window for debugging? @roblourens
    Rob Lourens
    @roblourens
    Sure, if the devtools are open in a tab which is in remote debug mode
    For your earlier question, no, workspaces are a chrome devtools feature and it works differently in vscode. I don't know why using fiddler as a proxy would impact debugging with vscode
    con-ssc
    @con-ssc
    @roblourens because I use Fiddlers autoresponder feature to hot swap the remote file with a local file, that does not work while vscode is debugging because that file does get encapsulated buy chrome and I cannot swap a chromedebugger embodying the file
    If you don't know what I'm talking about maybe this helps https://www.youtube.com/watch?v=h3DWqYXKarA
    Rob Lourens
    @roblourens
    I understand how fiddler works, I don't understand why it wouldn't work with vscode
    con-ssc
    @con-ssc
    it doesn't work with the vscode-chrome-debugger because the autoresponder substitution rule doesn't fit the chromedevtools url
    con-ssc
    @con-ssc
    Hmm maybe I also did something wrong, I tried to make an example for you and now it works as expected :+1: @roblourens
    Rob Lourens
    @roblourens
    great! :)
    Victor
    @oldbasilbear
    Hi folks. Can I reconfigure the extension to use Chromium (on Linux) rather than Chrome?
    con-ssc
    @con-ssc
    @oldbasilbear You can configure the runtime executable
    con-ssc
    @con-ssc
    is it possible to select one of the open chrome remote windows in the debugger in attach mode
    Rob Lourens
    @roblourens
    You can select it by setting the 'url' in your launch config, but that's the only selection mechanism i have right now
    con-ssc
    @con-ssc
    Hmm okay, because the url in my case is obfuscated by some internal routing
    I can get the url, but that wouldn't make any difference then between attach and open with that url
    damn I wish I could support you with that chrome debugger extension more :(
    Rob Lourens
    @roblourens
    The url can match with a if that helps. Like localhost:3000/page/*/foo
    Not sure how to escape the asterisk on gitter but hopefully you get the idea
    con-ssc
    @con-ssc
    Wildcards in the URL?
    I really need to get my hands dirty on the debugger somehow. I currently use fiddler with it and it works like a charm with live editing, except for no live reloading. Would be nice if I could somehow get rid of fiddler and let the debugger have its own intercept proxY
    con-ssc
    @con-ssc
    What would be your suggestion on where to start to get into the vscode chrome debug project @roblourens
    Rob Lourens
    @roblourens
    Plenty of bugs to fix ;)
    con-ssc
    @con-ssc
    @roblourens sure of that, but I need some general understanding first I guess, since this seems to be kind of two projects, the debugger and the core
    I would really like to help, but I guess I'm just not smart enough
    Rob Lourens
    @roblourens
    Right, so the vscode-chrome-debug-core project is used by vscode-chrome-debug and vscode-node-debug2. Most of the interesting code is in the core repo, so you'll want to clone both -core and vscode-chrome-debug, and use npm link to link them. Also see this file https://github.com/Microsoft/vscode-chrome-debug/blob/master/CONTRIBUTING.md and please help me fix it if anything is missing.
    krishnakrkhatri
    @krishnakrkhatri
    Has anyone faced "Server returned 400" error when trying to search for debugger-for-chrome extension under Extensions in VS 1.7.1 ?
    I even tried the offline method i.e., https://microsoft.gallery.vsassets.io/_apis/public/gallery/publisher/microsoft/extension/debugger-for-chrome/2.4.1/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage but didn't get lucky.
    con-ssc
    @con-ssc
    @krishnakrkhatri do you happen to have kaspersky internet security
    Azlan Mukhtar
    @azlan
    anybody able to debug vue.js (webpacked) from vscode?
    Azlan Mukhtar
    @azlan
    blob
    "webRoot": "${workspaceRoot}", "url": "http://localhost:8081/#/", "sourceMapPathOverrides": { "webpack:///./*": "${webRoot}/*", "webpack:///*": "${webRoot}/src/components/*" }
    Rob Lourens
    @roblourens
    What do you see if you type .scripts in the console while debugging?
    Azlan Mukhtar
    @azlan
    src\components\Login.vue?380c59aa (d:\codes\MyProject\dist\src\components\Login.vue)
    it should be
    src\components\Login.vue?380c59aa (d:\codes\MyProject\src\components\Login.vue)
    this is different project, not using webpack, but browserify
    Azlan Mukhtar
    @azlan
    both configs (webpack and browserify) work now, i will share to examples wiki later. thanks @roblourens
    Ruslan Kurchenko
    @henko-okdev

    Hello, guys.
    I'm new with vscode-chrome-debug and trying to debug my application that is hosted already.
    In details, I have an Angular app hosted by Salesforce on the url - https://trnc1srk1.na35.visual.force.com/apex/FormView.
    Could you provide me with info - can I debug code already deployed using "attach" option?
    All my attempts to connect to the app were failed.

    Here is my config for debugger:

            {
            "name": "Attach",
            "type": "chrome",
            "request": "attach",
            "port": 9222,
            "url": "https://trnc1srk1.na35.visual.force.com/apex/*"
        }

    And yes, I'm running Chrome with --remote-debugging-port=9222 parameter.
    Also, I work on Windows.

    Thanks.

    Rob Lourens
    @roblourens
    It's expected that you have the code in your workspace, if you don't already. But in what way did it fail?
    Ruslan Kurchenko
    @henko-okdev

    @roblourens I retrieve next exception:
    Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED 127.0.0.1:9222

    Also, I tried to add "webRoot": "${workspaceRoot}/pack/formview/app" config and it didn't help me

    Rob Lourens
    @roblourens
    That implies that chrome isn't listening on that port - see some troubleshooting tips here - https://github.com/Microsoft/vscode-chrome-debug#cannot-connect-to-the-target-connect-econnrefused-1270019222
    strongant
    @strongant
    Extension has not been invoked for the current page (see activeTab permission). Chrome pages cannot be captured.
    I have a try many times,sometimes is correct,sometimes is error?
    Ruslan Kurchenko
    @henko-okdev
    @roblourens you were right! I've closed all chrome processes and rerun it and debuger is working :) Thank you!
    José Diaz Seng
    @joseds
    Hi, I am learning how to use webpack via the SurviveJS book. I just went through the chapter on sourcemaps and tried to get debugging working in the current VS Code Insiders version. I created the following launch configuration:
    (sorry, hit return key too early..., details following)
    José Diaz Seng
    @joseds
        "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch index.html with sourcemaps",
            "type": "chrome",
            "request": "launch",
            "url": "http://localhost:4040/index.html",
            "sourceMaps": false,
            "webRoot": "${workspaceRoot}"
        }
    ]
    I am working on Windows 10 using a current version of Chrome.
    Now, my problem is that breakpoints are not being hit. When inserting a debugger; statement, execution stops there and I can step through my code, also the breakpoints in the code following are being hit. VS Code tells me "Breakpoint ignored because target path not found" on hovering over a breakpoint. Do you have an idea how to fix this? I would also be fine with an attach configuration.
    Rob Lourens
    @roblourens
    You have sourceMaps: false - maybe you are setting the breakpoint in a source file that isn't loaded in Chrome?
    Or you can use the .scripts command to see which urls are loaded. They will be resolved to files on disk using your webRoot - see if it makes sense.
    José Diaz Seng
    @joseds
    I have used sourcemaps generated by webpack. Juho Vepsäläinen (the author of the SurviveJS webpack book) suggested to use sourcemaps of type source-map insted of eval-source-map. This together with the following configuration 
        "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch index.html with sourcemaps",
            "type": "chrome",
            "request": "launch",
            "url": "http://localhost:4040/index.html",
            "sourceMaps": true,
            "webRoot": "${workspaceRoot}"
        }
    ]
    made it work, with eval-source-map it does not. I need to better understand what is going on. I will try using .scripts to see what goes wrong when trying to use eval-source-map.