Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    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
    ZMAN
    @Zii69_twitter
    I cannot seem to get this extension to work, my json settings unsure what to change. I tried to attach it as I have no idea how/what to setup with a web server.
    Screen recording 2017-08-17 at 10.37.10 AM.gif
    Image 2017-08-17 at 10.41.27 AM.png
    ZMAN
    @Zii69_twitter
    Please assist! :smile:
    Kenneth Auchenberg
    @auchenberg
    @Zii69_twitter Please make sure all Chrome instances are closed before you start the instance with remote debugging enabled. We recommend you using the launch config to avoid this
    ZMAN
    @Zii69_twitter
    @auchenberg I get the same error with all instances closed. I don't understand what to do with the other, launch config method. It is all kind of confusing.
    Kenneth Auchenberg
    @auchenberg
    @Zii69_twitter Please try to use the "Launch Chrome against localhost" configuration, which will launch a new Chrome instance with all the right parameters. You need to make sure you have a web server running the "url" defined. Per your config http://localhost:8080, that serves your files.
    Tommy Yang
    @M0gician
    Hi everyone, my chrome debugger stop working every time when I click "restart"
    [debugger-for-chrome] Error processing "restart": TypeError: Cannot read property 'Page' of undefined
    How can I deal with this problem?
    Rob Lourens
    @roblourens
    Please file an issue, sounds like a bug
    Check whether any other details show up in the console, and if you set "trace": true and include the full log, that would be very helpful!
    NAdhithya
    @NAdhithya
    Hi everyone, chrome debugger is not working in visual studio code but it was working till last week.I didn't change anything in config filr
    I'm getting following exception
    "Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule '@-moz-keyframes animation_16bh5sq{from{opacity:0;}to{opacity:1;}}'."
    Rob Lourens
    @roblourens
    That sounds like an exception from your app
    JAN
    @jjasoncool
    is "request": "attach" working?
    Rob Lourens
    @roblourens
    Should be, if not, provide some details
    JAN
    @jjasoncool
    when I attach to chrome or launch chrome I cant add breakpoint in line.
    and also cant attach to chrome.
    JAN
    @jjasoncool
    JAN
    @jjasoncool
    image.png
    JAN
    @jjasoncool
    image.png
    I put the attach setting in user setting or launch.json still doesnt work.
    JAN
    @jjasoncool
    sorry,
    i found the troble where I haven't setting vscode ["debug.allowBreakpointsEverywhere": false,] to true
    image.png
    after this it work.
    JAN
    @jjasoncool
    Is "skipFiles" support regular expression?
    Phil J
    @johnnyelwailer
    Hi. We set up debugging in an angular application, it used to work fine, but for a while now I always get the error message command 'extension.chrome-debug.startSession' not found
    The launch.json:
    {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "Launch Angular Client",
                "type": "chrome",
                "request": "launch",
                "url": "http://localhost:4200",
                "runtimeArgs": [
                    "--user-data-dir",
                    "--remote-debugging-port=9222"
                ],
                "sourceMaps": true,
                "trace": true,
                "webRoot": "${workspaceRoot}/Frontend/",
                "userDataDir": "${workspaceRoot}/.vscode/chrome"
            }
        ]
    }
    Steve Suranant
    @053steve
    Hi, I'm using node.js with es6. Everytime i start debuggin in vscode my breakpoint changes position (maybe because of babel compiling). Does anybody know how to make it properly debug in es6