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

dbg.log

v1.1.4

Published

Extended console.log, on condition from loca storage.

Readme

Leaving console.log messages in production is very unprofessional. What if we can see it in dev mode, but not in production.

You have 3 function's:

dbg.log()
dbg.group()
dbg.groupEnd()
dbg.table()

Use it in same way as standard console.log() console.group() console.groupEnd() and console.table()

Normal user will not see the dbg output in console devtools, unless your browser local storage have set item debug with value 1.

You cat set it by writing directly in your dev tools console:

dbg.on()
dbg.off()
dbg.toggle()

Check status, output to console.log() dbg.status()

Check status, return bool dbg.isDebug

cls is console.clear() - it is just less letters for clearing console to save your fingers.

Installation

Get it from npm

npm install dbg.log

or from github

git clone https://github.com/und3rdg/dbg.log

and place it in your code. dbg and cls have to by global variable.