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

lengthy-logger

v1.0.2

Published

a console.log alternative that tells you where you log is being called from (so you can delete it when you are finished with it)

Downloads

14

Readme

the lengthy logger

I used to get pretty frustrated when I would finish something and then need to remove all of my console.log()'s after loosing the context in my mind, so I made this kind of a logger to remind me exactly where I left my messages to myself. I will be expanding it so as to make it more fun to configure and use, drop feature requests into this repo's issues, and if you see anything wrong also let me know there. I hope that this is a helpful way to get a tiny bit more out of logging to the console 🤘

install

npm install --save-dev lengthy-logger

usage

super simple here

var log = require('lengthy-logger')

var object = {
  thing1: 'bar',
  thing2: true
}
var array = ['loo', 'tag', 'moo']

log('single string argument')
// output: file@/Users/yourusername/.../where/you/called/file.js@line12 🗣 single string argument
log('string1', 'string2', 'string3', 'string4')
// output: file@/Users/yourusername/.../where/you/called/file.js@line12 🗣 string1 string2 string3 string4
log('string', object, array)
// output: file@/Users/yourusername/.../where/you/called/file.js@line12 🗣 string
//  [{ thing1: 'bar', thing2: true }, ['loo', 'tag', 'moo']]