WebStorm Debugger
See original GitHub issueHow can we debug this using WebStorm?
I’ve tried running npm start
run configuration with the WebStorm debugger, but it quits the process once it reaches a breakpoint. I’ve tried the suggestion here, https://github.com/kriasoft/react-starter-kit/issues/396#issuecomment-171331792 and it will show that the debugger is started, but the process quits when a breakpoint is reached and a tooltip is displayed in WebStorm that says “connection refused.”
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
How to Debug With WebStorm - The JetBrains Blog
The debugger is one of the most essential features of WebStorm. With WebStorm you can debug all kinds of applications written in JavaScript, ......
Read more >Debug Tests in WebStorm | Debugging | Recipes | Docs
Debug Tests in WebStorm · Step 1 - Install TestCafe · Step 2 - Add a Command To Debug TestCafe · Step 3...
Read more >Debug JavaScript code from WebStorm or IntelliJ IDEA
4. Set a breakpoint in your source file and click on debug icon (shift+F9) for the just created debug configuration. The IDE and...
Read more >How to Debug Node Serverless Using JetBrains WebStorm
When I went looking how to debug serverless, I struggled to find a solution that detailed debugging serverless in JetBrains WebStorm.
Read more >WebStorm JavaScript debug terminal - node.js - Stack Overflow
In WebStorm you can run certain commands like npm run <command> and usually it will be highlighted in green which means you can...
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
Apparently the process quits because node is running under a child process. What I did was add the --debug arg under the runServer.js and create a remote debugger.
... cp.spawn('node', ['--debug', serverPath] ...
It isn’t the best solution due I have to run the npm start first but at least the npm start and debugger work together.