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 🙏

© 2026 – Pkg Stats / Ryan Hefner

debugutil

v1.5.2

Published

Debug Utility Tool with Logging

Readme

debugutil

A NodeJS API debug utility tool with logging developed for my Deployment of Web Applications class at Full Sail University. This package will allow you to debug your API with success, warn and error messages displayed in your CLI (Command Line Interface) as well as saving timestamped messages to a .log file.

Note: Logging is not working. I will have this fixed soon.

Required

This Debug Utility Tool will run on an API created with NodeJS

Installation

In your CLI, ensure that you are in the directory containing your NodeJS API.

Run the following to add debugutil to your node_modules and your package.json file dependencies:

npm install debugutil

Dependencies

After installation, run the following to install the dependencies required to properly run debugutil:

npm install

Debugging

You will need to require the debugutil package in each file you wish it to run. You can do this by adding the following to the top of each file:

require('utildebug');

To enable logging, use the following environmental variable:

DEBUG=true

You will now receive green success, yellow warn and red error messages in your CLI as well as have them logged to the .log file located in the logs folder.

To disable logging, use the following environmental variable:

DEBUG=false

Unit Testing

This package has been Unit Tested using chai and mocha. You will need to install these packages to your devDependencies to run tests.

To run tests, execute the following command in your CLI:

DEBUG=true mocha

Code Coverage

Check out istanbul for more on code coverage.

To run tests with code coverage, execute the following command in your CLI:

istanbul cover src/debug.js

Other

You can change the name and/or path of the folder and the .log file, in src/debug.js. Just edit the following lines:

fs.appendFile('./logs/logFile.log', function () {
  console.log('Data was successfully appended to file!');
});

You can change the display color of messages in src/debug.js via chalk by editing the following:

const success = chalk.green;
const warn = chalk.yellow;
const error = chalk.red;