Better tools for debugging Node.js

Debugging – the process of finding and fixing defects in software – can be a challenging task to do in all languages. Node.js is no exception. Luckily, the tooling for finding these issues improved a lot in the past period. Let’s take a look at what options you have to find and fix bugs in…

I am at the level with Node.JS that I no longer “Suck at it” but I am still learning every time I use it.  One of the areas I struggled with was debugging, which was much different and difficult than my .NET and PHP days.  It seems like open source meant that you were on your own for debugging.

Special thanks to Gergely for his article on just the topic of Node.js debugging.

pino.pngOne of the takeaways in the article is Pino is an extremely fast Node.js logger, inspired by bunyan. In many cases, pino is over 6x faster than alternatives like bunyan or winston
I had tried Winston as it was recommended by one of my programmer gods.  I was not worthy because I couldn’t understand it.  I have high hopes for Pino.

I use Microsoft VS Code editor as my editor and my IDE for almost everything including PowerShell, Bash, JavaScript, SQL, Node.js, ADCIIDoctor, and more.  I was glad to see a section in this article on how to better use MS Code with Node.js

via How to Debug Node.js with the Best Tools Available — RisingStack Engineering