Debugging Node.JS!

As per Hofstadter’s Law, it always takes longer than we expect to implement any development feature. Bugs are a byproduct of code. On a lighter note, the number of lines of code is directly proportional to number of bugs. So, debugging is one of the essential skills every developer should have. The more knowledge about the local variables and flow of control, the easier it is to triage bugs and fix them.

Javascript is one of the popular languages and Node.js proved quite efficient for highly scalable, data intensive and real time apps. Learning Node.js development with novice knowledge in javascript, the first thing I learned is debugging. Here are the three techniques to debug a Node application:

Log to console:

global.console.log(“This is a wanderers web debug post !”)

Throw Exceptions:

Below shows an example to throw exception:

Throw Error(“This is a wanderers web debug post !”);

Debug with IDE:

// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit:
"version": "0.2.0",
"configurations": [
"type": "node",
"request": "launch",
"name": "Launch Program",
"skipFiles": [
"program": "${workspaceFolder}/dist/index.js",
"preLaunchTask": "tsc: build - tsconfig.json",
"outFiles": [

Debugging is one of the most underrated skill to learn a new language. Above techniques can be used to understand existing Node.js application or implement a greenfield project.



Curious Human, Software Developer and a Dog Lover

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store