Summary
Logpoints and conditional breakpoints, set from the same place you are asking about the bug.
The useful move here is the logpoint: set a breakpoint that prints an interpolated message instead of halting, so you get the value of a variable at a line without stopping the app or editing the file. Errors and violations also stream, so a long session does not need polling.
What it is
A development companion for React and Next.js work. It drives Chrome through Puppeteer to capture errors and network activity, watches files for complexity and rule violations, and manages breakpoints — all reachable as tool calls.
What you get
- get-errors — caught and uncaught errors, console errors and promise rejections, filtered by severity or timeframe
- get-violations — code-quality rule violations, by severity or by file
- analyze-complexity — cyclomatic complexity, function metrics and nesting depth for one file
- get-performance — render times and performance metrics over a timeframe
- manage-breakpoints — set, remove and list breakpoints, including conditional ones and logpoints that log instead of stopping
- get-debug-session and update-config — the current session, and changing the debugger's settings mid-flight
- Three live resources: stream://errors, stream://violations and stream://performance
Requirements
Node — clone, npm install, npm run build, then point the client at the built dist/index.js. No credentials.