From ae959049e47a2063da66f35dbac1fe41bdadeb66 Mon Sep 17 00:00:00 2001 From: Aarti Verma <75892381+vermaaarti@users.noreply.github.com> Date: Wed, 12 Oct 2022 03:27:08 +0530 Subject: [PATCH] Added content for debugging in node.js and how to debug. (#2340) * Added content for debugging in node.js and how to debug. added tutorial links for the same to learn more about debugging in node.js * Update content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/readme.md Co-authored-by: Kamran Ahmed --- .../content/116-nodejs-more-debugging/readme.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/readme.md b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/readme.md index d5c95c71d..5b0f65a73 100644 --- a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/readme.md +++ b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/readme.md @@ -1 +1,9 @@ -# Nodejs more debugging \ No newline at end of file +# 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