question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The debug console is slow when run without debug with pwa-node

See original GitHub issue

Describe the bug I have just found that the new JavaScript debugger is slow when I launch Node.JS app. The default configuration for Node.js is

"configurations": [
        {
            "type": "pwa-node",
            "request": "launch",
            "name": "Launch Program",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "program": "${workspaceFolder}\\src\\index.js"
        }

The debug console do logging with long delay, like this video: https://drive.google.com/file/d/1w6EEpYfDrv67RhKYm7aghf9Spi6kvBm9/view?usp=sharing

But when I change the type to node: "type": "node" the debug console run way faster: https://drive.google.com/file/d/1OGeFpXrAPj2KspMwnbvPf6SVufHgRooh/view?usp=sharing

To reproduce

  1. Open project folder in VSCode (here is my project folder zip https://drive.google.com/file/d/14jR3RJWnLKFZezmMir6qSSOMUIqGMd6s/view?usp=sharing)
  2. Run without debug (ctrl + F5)
  3. Open postman
  4. Make a GET request to localhost:3000/users/45645132131 or any id string after “users/”
  5. Come back to VSCode and wait for the id to be logged in debug console
  6. In lauch.json, change "type": "node" and do the same steps above then see the difference in those to debugger

VSCode version: 1.59.0 (user) stable Windows 10 64bit NodeJS version: 14.16.0

Additional text: Unfortunately, Node (legacy) was deprecated and is going to be replaced by this new debugger (pwa-node). Is this a bug and will it be fixed in the future? I’m really sad to know that the simple Node debugger was to deprecate.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
connor4312commented, Aug 7, 2021

Thanks, this’ll be fixed in the next nightly release on Monday (note that VS Code Insiders is required).

0reactions
catan271commented, Aug 26, 2021

I have tried the nightly release and version 1.60.1 in vscode insider. The bug has been fixed. Hope to see it fixed in the stable version of vscode.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Extremely slow debugging Node JS if any breakpoint exists ...
Issue Type: Bug Steps Create a new folder and open it with VSCode Create a new test.js file and type in console.log("Hello") Go...
Read more >
VS Code Debugger Extremely Slow to Reach First Breakpoint
I'm using VS Code on Windows 10, to debug both Python and React. The debugger is extremely slow to reach the first breakpoint, ......
Read more >
How to debug Node.js apps in Visual Studio Code
The easiest way to start a debugging session in Visual Studio Code is to open a file in the editor, click the Run...
Read more >
Program Runs Slower When Using "Start Without Debuggin"
When I execute the program by "Start with Debugging" the code performs perfectly. No breakpoints, just execute the program.
Read more >
How to Debug Node.js Program with VS Code? | by Zachary Lee
This article (I will focus on how to debug Node.js programs in VS Code) ... does not “break” into the debugger but instead...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found