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.

Error stack is not sourcemapped #212

@AskYous

Description

@AskYous

I am receiving an error from VSCode saying it cannot find the file when I click on the source of an error in chrome from the VSCode debug console. I am running Debugger for Chrome version 3.1.2. I posted a screenshot below. Notice a couple of things:

  1. My website is running on localhost:1337. For some reason, VSCode is trying to open the file in /1337/js/components.js. (How did the port get into the source path???)
  2. I have source mapping on for my typescript files.
  3. The file open is the launch.json file shown in the screenshot. I pointed the webRoot folder to my assets folder, yet it seems to completely ignore it.

image

Update: I ran this with "trace": true. Here is vscode-chrome-debug.txt.

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