npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

debug_utility_tool

v1.0.4

Published

This is a better way to console log and log in general

Downloads

16

Readme

Debug Utility Tool

This is a very easy to use tool that intends to help making logging and console.logging rich. This tool will allow you to have detailed message of what is going on with your project while debugging.

As developers we are constantly console.logging here and there to check what is returned, what is contained in a variable or to simply add tracks to know how the code is executing.

This tool allows you to set a message and everything else is done for you. The tool will give you the line and file the error happened at, who called, what method was used and if any data was returned and display it nicely.

console

Installation

Use the following command to install it:

npm install debug_utility_tool

Usage

You can simply require it to a variable and start using it.

require

Turn Debug Mode ON

This module blocks any console log among your code so to use this module you must first turn DEBUG mode ON:

Lets say you want to run server.js on debug mode

node server.js --debug true

or

node server.js -d true

Both ways you can set DEBUG on

.debug

The .debug funtion allows for 3 optional parameters and 1 required.

You must provide a message to it

util.debug('This message is required');

Specify a Message Type

util.debug('This message is required', 1);

You can pass it a 0, 1, or 2 and it cannot be a string;

  • 0 = Error;
  • 1 = Warn;
  • 2 = Info;

By default and message is set to be a Mesg defaultMsg

Pass some DATA

if you simply want to check what data is returned or being processed you can simply pass it as the 3 argument. This means that at this point you must specify a message type.

for example:


let n = 4;

function foo(number){
    util.debug('what is the number?', 2, number)
}

foo(n);

// --- outputs
/*- Debugging -----------------
    Time: 0:15 20
    Info: what is the number?
    Line: 7
    File: /Users/ecorreia/Sites/_tests/debugTool/node_modules/caller-id/lib/caller-id.js
    Func: getData | type: Object | method: getData
    Data: number 4
*/

Callback function

util.debug('what is the number?', 2, number, function (err) {
    if(err == 0){
      // do something
    }else{
      // do another
    }
  })

This callback function is used to see if the tool did its job or failed. You will double check if the tool threw an error and you didnt happen to catch it.