Node.js Diagnostic Best Practices
summary
Documentation maps concrete flows for debugging Node.js services: step‑by‑step user journeys that align tools to real incidents and include setup instructions, investigation flows and case studies. Current guides cover memory profiling and abnormal termination, with work in progress for crash, hang and tracing scenarios. Tools referenced include llnode and diagnostic report and the project classifies tooling by tooling tiers to guide release and contributor focus; the repo backlog shows item 439 as the top-level worklist. Contributions and real-world reports are requested.
AI-written summary · about
chapters (5)
related talks
29mNode.js Diagnostic Best Practices
25mNode js applications diagnostics under the hood
23mThrow Me a Lifebuoy: Debugging Node.js in Production with Diagnostic Reports
28mDiagnostic Tooling - Be Ready when Things Go Wrong in Production
21mFoundations of Debugging Node.js
57mTroubleshooting Node.js Applications Under the Hood
50mPost-Mortem Debugging in Node.js
31mConsole.loggers Anonymous: A Debugging Roadmap from Local to Production