node-inspect-debugger

To debug a Node.js application, you can set breakpoints at the file, line, or function level using the built-in `node inspect` command. Start by running your script with `node --inspect-brk script.js` to pause execution and step through code interactively.

Yes, you can evaluate expressions directly within a paused frame during Node.js debugging. This allows you to inspect variable values and test logic interactively while execution is halted at a breakpoint.

The best way to capture CPU profiles and heap snapshots in Node.js is by using the Chrome DevTools Protocol via `chrome-remote-interface`. This enables automated, scriptable performance profiling to analyze bottlenecks and memory usage.

Yes, Node.js debugging works seamlessly with the Chrome DevTools Protocol for automated testing. Using the `chrome-remote-interface` dependency, you can script debugging actions like pausing execution, setting breakpoints, and inspecting variables programmatically.

You need to use `--inspect-brk` to start debugging a Node.js script because it pauses execution on the first line before any code runs. This ensures the debugger is attached immediately, allowing you to set early breakpoints and trace issues from the start.