Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

184
Views
VS Code Debugging problems after last update (1.69.2)

After the last update of VS Code to version 1.69.2 i am not able to debug my nodejs - express, project. I am getting unbound breakpoints when i am adding them. My launch.json file :

{
    "configurations": [
    {
        "name": "Attach by Process ID",
        "processId": "${command:PickProcess}",
        "request": "attach",
        "skipFiles": [
            "<node_internals>/**"
        ],
        "type": "node",
        "sourceMaps": false
    }
    ]
}

When i am trying to "troubleshoot the launch configuration" i am getting the error message from vs code : "it looks like your degug session has already ended......" but it is not, it is active.

In my project i am using nodejs - express - javascript mostly (no Typescript thats why i set sourceMaps to false).

I am starting my project with the command : node --inspect sever.js and after that i attach by procces the debugger ( to default 127.0.0.1:9229).

Can anyone help me to solve this problem? What has change after the last update and i can't use the degugging of VS Code? Thanks a lot.

about 4 years ago · Santiago Trujillo
1 answers
Answer question

0

Download a previous version. Also, disable auto updates from Settings -> Update. https://code.visualstudio.com/updates/v1_68

about 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!