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

utility-tool-sd

v1.1.0

Published

Debug tool on NodeJS

Downloads

13

Readme

This tool only triggers if the environmental variable DEBUG is set to true. To run it, turn on the server with DEBUG=true node src/app.js.

Usage

Debug

To run it simply do this:

const util = require('utility-tool-sd');
const path = 'src/routes/api/api.js';
util.debug('My message', 'src/myApp.js', 'success');

Utility tool accepts 3 arguments: message, path, and level. message is whatever goes after SAYS: (see an example of output below). path is a path of file from which this message is coming from, which you should type manually. level is an importance of message. All of these variables are optional, but it would make a lot more sense if you define all of them.

Debug tool spits data to console and to logs/debug.log file, so make sure to create a logs folder in the root of your project. In console messages are colored, depending on the level. There are 4 levels of messages: notice (or n), success (or s), warning (or w, or warn), and error (or e, or err). They are colored in blue, green, yellow, and red respectively. In log file the messages may look somewhat like this:

NOTICE [Sat Dec 03 2016 21:33:15 GMT-0500 (EST)] FILE: src/app.js SAYS: "Server running on port 3000"

Bump

Bump accepts a semantic version argument and a type in which to semantically increment the version. It will then return the desired new semantic version number as a string.

How to use bump:

const util = require('./util');
const patch = util.bump('3.3.3', 'patch');