Using breakpoints doesn't work when debugging
See original GitHub issueMy npm script is as follows:
{
...
"scripts": {
"start": "babel-watch --debug 5859 src/backend/index.js",
...
},
...
}
I get the Debugger listening on [::]:5859
message and my debugger is able to connect on port 5859
, but putting breakpoints in my IDE (JetBrains WebStorm) appears to do nothing, making debugging effectively useless.
Using the --debug-brk option also screws up the debugging process, making it break on the underlying runner.js
file instead of the script we want it to run on.
Any ideas how to make breakpoints work?
babel-watch
version is 2.0.6
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Visual Studio debugger doesn't stop on breakpoints
Right-click your project from the Solution Explorer, and then click Properties. Click the Web tab. Under Debuggers, check the ASP.NET checkbox.
Read more >Visual Studio breakpoints not being hit - Stack Overflow
One more thing, change from Release to Debug mode. In release mode PDB files are not getting updated with breakpoints details. So make...
Read more >BreakPoints Are Not Working in Visual Studio - C# Corner
Solution: Start debugging. As soon as you've arrived at a breakpoint or used Debug > Break All, use Debug > Windows > Modules....
Read more >VS2022 does not stop at breakpoints. - Visual Studio Feedback
I developing using Xamarin Forms. Fixed In: Visual Studio 2022 version 17.1Visual Studiowindows 10.0debuggervisual studiovisual studio 2022 version 17.0.1.
Read more >Debug Breakpoints not working #45657 - microsoft/vscode
The best workaround for people using 1.21 is to set the outFiles parameter in your launch config so that the adapter can load...
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
Progress on this?
#62 merged via #118 and released in
7.3.0
.