No way of debugging node server
See original GitHub issueRunning node --inspect node_modules/razzle/scripts/start.js causes the server-side reloader to get stuck on the first debugger statement but the debugger itself never reacts and none of the server-side files are available to open and add breakpoints.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Debugging - Getting Started - Node.js
Create a new Node.js debug configuration and hit Debug. --inspect will be used by default for Node.js 7+. To disable uncheck js.debugger ......
Read more >Debug Node.js Apps using Visual Studio Code
There are a few ways you can debug your Node.js programs in VS Code: ... the JavaScript Debug Terminal will automatically debug any...
Read more >Running and debugging Node.js | WebStorm Documentation
Debugging a Node.js application · Run your application with an --inspect or --inspect-brk flag. You can do that in several ways, for example:....
Read more >How To Debug Node.js with the Built-In Debugger and ...
When debugging in Node.js, we add a breakpoint by adding the debugger keyword directly to our code. We can then go from one...
Read more >How to Debug Node.js Code Using Multiple Tools - Kinsta
This tutorial demonstrates various tools to debug node applications and find their root causes. Dig in and learn from the ground up.
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 Free
Top 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

Shnice. Thanks. Will play with this tonight / tomorrow (at React Rally right now)
Fixed w/ #333