github
/
developer-roadmap
mirror of https://github.com/kamranahmedse/developer-roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Roadmap to becoming a developer in 2022
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2308 Commits
193 Branches
4 Tags
439 MiB
 
 
 
 
 
Tag: Branch: Tree: 7c73452438
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7c73452438'
${ noResults }
developer-roadmap/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging
Aarti Verma ae959049e4
Added content for debugging in node.js and how to debug. (#2340) 		2 years ago
..
100-memory-leaks Added content on memory leaks, its causes and its detectors (#2342) 2 years ago
101-node-inspect.md Added node inspect content (#2346) 2 years ago
102-using-apm.md Added content for Debugging using APM (#2347) 2 years ago
readme.md Added content for debugging in node.js and how to debug. (#2340) 2 years ago

readme.md

More Debugging

Debugging is a concept to identify and remove errors from software applications. Here, we will learn about the technique to debug a Node.js application.

Why not to use console.log() for debugging?

Using console.log to debug the code generally dives into an infinite loop of “stopping the app and adding a console.log, and start the app again” operations. Besides slowing down the development of the app, it also makes the writing dirty and creates unnecessary code. Finally, trying to log out variables alongside with the noise of other potential logging operations, may make the process of debugging difficult when attempting to find the values you are debugging.

Free Content Node.js Debugging