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 🙏

© 2025 – Pkg Stats / Ryan Hefner

debug-instanced

v1.0.0

Published

Like the 'debug' module, but automatically labels output with an instance ID. Useful when dealing with many different objects.

Readme

debug-instanced

Like the debug module, but automatically labels output with an instance ID. Useful when dealing with many different objects.

Usage

See also example.js in the package.

"use strict";

const debugInstanced = require("debug-instanced")("example");

function doThing() {
	let debug = debugInstanced("foo");
	debug("line one");
	2 + 2;
	debug("line two");
}

doThing();
doThing();

This would output the following:

~/projects/debug-instanced> DEBUG=* node example.js
  example [e04ab8] created instance (type: foo) +0ms
  example [e04ab8] line one +1ms
  example [e04ab8] line two +0ms
  example [931af6] created instance (type: foo) +0ms
  example [931af6] line one +1ms
  example [931af6] line two +1ms

As you can see, the output from each 'instance' of the call to doThing is labelled with its own unique ID, that is generated when debugInstanced is called.

The API is basically the same as that of debug, except there's an extra level of function invocation. Normally when you call the function exported by debug you immediately get a function that lets you log things; but in debug-instanced, that gets you an instance creation function instead. That instance creation function, when called, returns the logging function you need - and it's called the same way as the logging function in debug.

The enabled property is available on the instance creation function, instead of on the logging function where it would be in debug.