🐢 Node.js

🔍 Debugging & Profiling

Improving on topics like debugging is very important as a developer in order not to be lost on what to do when you encounter a hairy problem (which will require a little more than some console.log).

Note however that if you need to go that far, there may be a problem in the way you architect your code.

Here is a list of resources that you may need to read:

• Node.js debugging best practices
• Node.js official debugging guide
• Node.js debugger API
• VS Code integrated tools for Node.js
• Easy profiling for Node.js Applications
• Create a Dump of the V8 Heap in Nodejs
• Node.js console API (there is not only console.log ^^).
• Clinic.js rises to the top in diagnosing Node.js performance issues
• Node.js Memory Limits - What You Should Know
• The Importance of Measuring Memory Allocation in Node.js Applications
• Monitoring Node.js Performance

If you are rather looking for tools (for flamegraphs generation for example).

• 0x🔥
• Node-observe
• ClinicJS
• trace GC
• Why is node running (cool to find alive event loop references).

If you need to benchmark your tests then I recommend autocannon.

---

⬅️ 🐢 Node.js: 📦 Packages | ➡️ 🐢 Node.js: Modules (CJS & ESM)