Skip to content
This repository was archived by the owner on Oct 2, 2021. It is now read-only.
This repository was archived by the owner on Oct 2, 2021. It is now read-only.

Path mapping of source files in stack traces not working #198

@aramando

Description

@aramando

Despite this feature having been implemented and working for some (see #6) I'm still not seeing my Javascript sources' URLs being mapped to their local paths in stack traces in my debug console, which look like this:

TypeError: bounds.aspect is not a function
    at Size.resizeToFit (http://localhost:3000/js/Geometry.js:103:31)
    ...

The part of the URL after the protocol is clickable, but results in a file not found error. By the way I'm talking about plain JS files with no sourcemaps. My debug launch config looks like this:

{
    "name": "Launch localhost",
    "type": "chrome",
    "request": "launch",
    "url": "http://localhost:3000",
    "webRoot": "${workspaceRoot}/client"
}

Everything is bang up to date:
Code v1.11.1
Debugger for Chrome extension v2.7.3
Chrome version 57.0.2987.133

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions