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

utilitytoolwash

v1.0.8

Published

Downloads

35

Readme

Documentation for NPM package utilitytoolwash v1.0.2

Codeship Status for URL Shortener

Powered by Washeen Orlando SEO

npm i -s utilitytoolwash

How to Use the Package

Debuging

First, the environmental variable DEBUG needs to be set to true for logs to print out to the console. like so...


DEBUG=true node src/server.js

Example

// Call The Module into a script
const dataLog = require('utilitytoolwash').debug;

// if stat is not defined then 'log' will be the default
// if no error is passed in a default message of 'no errors' will display in it's place
dataLog('Our Server is Running', port);

// set a log to catch a warning
dataLog('Log a warning', port, null, 'warning');

// for logs that might catch an error
const err = new Error();
dataLog('To catch an error', port, err, 'error');

Make sure to follow these steps when using the data to log into your log directory.

If you want to be able to catch an error pass in the error as the first parameter

// Call The Module into a script
const dataLog = require('utilitytoolwash').debug;

//Used: date, message and object in it.
dataLog(err, 'Our Server is Running', port);

If you want an err is not defined in the same scope as dataLog then pass in null as the first argument.

Make sure when adding your dataLog(); first comes the error, then the text message which explain the function or process that you wanna console.log out to the .log directory and finally the object you are using.

Version Bumper

This package has a version bumper feature. You can require it to be used to bump the current version stated in the package.json file.

Ther first parameter should be the version you want bumped up. The intent for this version bupmer is for the version of the package.json file. You can single out the version in the package.json using require(). For example:


const version = require('./package.json');

This function bumps up the version based semantic versioning: MAJOR.MINOR.PATCH This function takes 1 of 3 values as the second argument: major: bumps current version up 1 major version minor: bumps current version up 1 minor version patch: bumps current version up 1 patch version

Examples:

// create an instance of the version bumper
const versionBumper = require('utilitytoolwash').versionBump;
const version = require('path/to/package.json');

// package.json current version is 1.0.0

// bump up 1 major version
versionBumper(version, 'major'); // returns 2.0.0

// bump up 1 major version
versionBumper(version, 'minor'); // returns 1.1.0

// bump up 1 major version
versionBumper(version, 'patch'); // returns 1.0.1