[Debug: Create JavaScript Debug Terminal] Executing the script does not trigger debugging
See original GitHub issue- VS Code Version: 1.43.2
- JavaScript Debugger (Nightly) Version: 2020.5.2617
Steps to reproduce:
- Create a one-off terminal for debugging via the Debug: Create JavaScript Debug Terminal command
- Execute the script command on the terminal created in the previous step, but the debugging process is not triggered
I added the following configuration into the settings.json
:
{
"debug.javascript.usePreview": true,
"debug.javascript.debugByLinkOptions": "always",
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Debug Node.js Apps using Visual Studio Code
You can create a Debug Terminal by running the Debug: Create JavaScript Debug Terminal command from the Command Palette ( kbs(workbench.action.showCommands) ), ...
Read more >Tests with debug do not start with Javascript Debug Terminal
I have just tried it with new nestjs project. Just run app.controller.spec.ts, insert the script in my question and you will reproduce. But,...
Read more >Easily debugging client side code with a JavaScript ... - YouTube
... a link to a site in a JavaScript debug terminal and VS Code wil... ... No configuration required. https://github.com/microsoft/vscode-j.
Read more >How to Debug JavaScript in Visual Studio Code - YouTube
In this tutorial, I'll show you how to set up JavaScript debugging for Visual Studio code, including debugging React applications.
Read more >Debug a JavaScript or TypeScript app - Visual Studio (Windows)
When using Chrome, you might get a message "no source is available between <script> tags". It's OK, just continue debugging. For Microsoft Edge ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I forgot that the shell variables can be concatenated, and now it works well:
Thank you for the help! I’m sorry I didn’t check my shell variable configuration when I knew
NODE_OPTIONS
was a key environment variable.Yes, you are right, I found this environment variable declaration in
~/.bashrc
:This may be the solution I found to alleviate the memory consumption problem of Node.js (I can’t remember the details), can I let it continue to work?