Visual Studio Code unbound breakpoint Node JS React TypeScript

Question

When I try to put a breakpoint and start debugging, the breakpoint becomes hollow and unbound.

Does someone know how to fix this problem? I've already looked around and tried and nothing helped so far...

I'm using VSCODE NODEJS REACT TYPESCRIPT

launch.json

tsconfig.json

Yotam · Accepted Answer · 2021-07-22 12:10:54Z

8

Solved it by opening the terminal first, "npm start" then pressing F5 to start debugging.

answered Jul 22, 2021 at 12:10

Yotam

3431 gold badge2 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Playing With BI Over a year ago

Cannot do it in my case because I don't have node in my local computer but on the docker image running the react app.

PlayHardGoPro Over a year ago

@PlayingWithBI found a solution? I'm in the same situation

Baga · Accepted Answer · 2022-05-15 08:54:59Z

8

Setting sourceMap to true in tsConfig.json solved the issue.

{
  "compilerOptions": {
    ...
    "sourceMap": true
    ...
  }
}

answered May 15, 2022 at 8:54

Baga

1,47217 silver badges25 bronze badges

Comments

Alexander Khomenko · Accepted Answer · 2024-02-13 12:27:31Z

1

Well, I just had the same problem on an open source project. I tried several things, like updating the VSCode, "sourceMap" was already true, but nothing helped.

Then I realised that there were discrepancies in launch.json: While the whole project was working on the "dist" directory, launch.json was working on "out".

Now it works as expected. Of course I will create a pull request.

answered Feb 13, 2024 at 12:27

Alexander Khomenko

5971 gold badge5 silver badges14 bronze badges

Collectives™ on Stack Overflow

Visual Studio Code unbound breakpoint Node JS React TypeScript

launch.json

tsconfig.json

3 Answers 3

2 Comments

Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

launch.json

tsconfig.json

3 Answers 3

2 Comments

Comments

Comments

Related