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

Node-Log

v1.0.0

Published

*******************************Utility Tool Usage************************************

Readme

Utility Tool Usage*****

In order to use this Utility tool it must be installed via NPM and required via require('path/debug');

When used with a function or any other block where a developer would normally console.log out some information the tool may be called by using debug.log('Information wishing to be stored in a log to be reviewed'); after doing so the tool will write a file called log.txt in the project directory adn this is where the logs will be sent. The logs can be as intricate or as simple as the developer would like them to be.

Example******************

// Logging function for when a request is made

if (success) { debug.log('The find all request for the url model was successful. Route: /urls'); } else { debug.log('There was an issue with your request this is a warning please look into the findAll function. Route: /urls'); }

By including a if/else statement inside of a function the user may test if the function was successful or not and also test specific values.