FEEL FREE TO SHARE TUTORIALS, YOUR SKILS & KNOWLEDGE ON CODING, SCRIPTS, THEMES, PLUGINS OR ANY RESOURCES YOU HAVE WITH THE COMMUNITY- Click Here To Post Your Request,
JOIN COMPUTER REPAIR FORUM

Reply to thread

Message: <blockquote data-quote="codeguru" data-source="post: 58" data-attributes="member: 2">Proper logging is of massive utility for web apps, both during development and after deployment.  What can sometimes be difficult is organizing both the code and output of logging, i.e. knowing where each log message is coming from.  I recently found <a href="https://github.com/visionmedia/debug" target="_blank">[ICODE]debug[/ICODE]</a>, a Node.js utility for organized and optimized debugging.Creating an instance of [ICODE]debug[/ICODE] is simple and you can create multiple loggers per file:// Create multiple instances of debug// In theory these would serve two different purposesvar debuggerA = require('debug')('worker:a'),    debuggerB = require('debug')('worker:b');// Sample usages of the debuggerfunction work() {  debuggerA('doing lots of uninteresting work');  setTimeout(work, Math.random() * 1000);}work();function workb() {  debuggerB('doing some work');  setTimeout(workb, Math.random() * 2000);}workb();<img src="http://davidwalsh.name/demo/debug-worker.png" alt="Node.js Debug" class="fr-fic fr-dii fr-draggable " style="" />The namespace given to a [ICODE]debug[/ICODE] instance as you must use an environment variable to signal which loggers should go to STDOUT when the script is run:// Show all debugger messages prefixed "worker:_____"DEBUG=worker:* node app.jsThe environment variable strategy for signaling which instances should output is brilliant as you may want only certain types of messages logged in production vs. development.  Use namespaces wisely!I was also able to use [ICODE]chalk[/ICODE] to color messages as desired:var chalk = require('chalk');debuggerA(chalk.red.bold('OMG an awful error!'));[ICODE]debug[/ICODE] is one of those utilities that has a very simple purpose and accomplishes the task well.  Don’t skimp when it comes to logging informative messages — they’ll help you during development and could be critical when auditing the app after a security incident!The post <a href="https://davidwalsh.name/node-debugging" target="_blank">Node.js Debugging</a> appeared first on <a href="https://davidwalsh.name" target="_blank">David Walsh Blog</a>.<a href="https://tkjs.us/dwb" target="_blank"><img src="https://davidwalsh.name/demo/tjs_block-1.svg" alt="" class="fr-fic fr-dii fr-draggable " style="" /></a><a href="https://davidwalsh.name/node-debugging" target="_blank">Continue reading...</a></blockquote>

Verification

Richest Freecoded User

Most Freecoin

freecoded

4,838 Freecoin

Davy200

590 Freecoin

Johnhendrick

575 Freecoin

Smith16

527 Freecoin

nathan69

426 Freecoin

Laureine

415 Freecoin

anajeen

370 Freecoin

codeguru

287 Freecoin

Tekera

267 Freecoin

Akubay

170 Freecoin