Node.js engineers spend significant amounts of time developing from the console. The usual workflow I’ve encountered goes something like: npm run test && node index.js which then dumps pages of text to stdout . Errors can easily go unnoticed when large volumes of output are generated by your app. While this environment can be productive, we miss out on insights into the process itself. Sure you can open top to retrieve process info, or go even further by instrumenting your code when something goes wrong. But why reproduce this in an ad-hoc manner when you can use nodejs-dashboard to send real-time telemetry to the console?Check it out in action:
For the initial release, we support the following features:stdout/stderr: Stream stdout and stderr to separate panes CPU Utilization: Real-time CPU utilization Event loop delay: Real-time event loop delay with high-water tracking Memory: Heap consumption and resident memory Ready to take your Node.js development experience to the next level?
View the source code for nodejs-dashboard on Github.