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

debug3

v1.0.8

Published

a tiny debugging wrapper on top of `debug` to improve performance

Downloads

34

Readme

debug3

npm version Build Status Coverage Status FOSSA Status Greenkeeper badge

A tiny debugging wrapper on top of debug

The main difference is that debug3 accepts functions as arguments and does not execute them unless it will output something (ie process.env.DEBUG is set to the relevant value).

This saves valuable processing resources that may have been used to create debug output that might not even be displayed.

Bonus: Package name of the calling module is prefixed to the debug message (can be turned off)

Installation

$ npm install debug3

Usage

debug3 exposes a function; simply pass this function a namespace, and it will return a decorated version of console.error for you to pass debug statements to.

Pass this resulting function any type of object, including functions.

Example

(In these examples package.json has a name of super-server which you can see in the output)

Basic Example

const debug = require('debug3')('http');

debug('This is a debug test!', [1, 2, 3]);
// Output: **super-server:http** This is a debug test! [1, 2, 3]

Passing a function

const debug = require('debug3')('http');

// ES6
debug('This is a debug test!', () => [1, 2, 3]);
// Output: **super-server:http** This is a debug test! [1, 2, 3]

// ES5
debug('This is a debug test!', function() { return [1, 2, 3] });
// Output: **super-server:http** This is a debug test! [1, 2, 3]

Turning off the package name prefix

const debug = require('debug3')('http', {prefix: false});

debug('This is a debug test!', [1, 2, 3]);
// Output: **http** This is a debug test! [1, 2, 3]

Comparison

Original debug

const debug = require('debug')('http');

debug('This is a debug test!', [1, 2, 3], JSON.stringify(largefile));
// With process.env.DEBUG === 'super-server:*'
// Output: **super-server:http** [1, 2, 3], {"large-json-file": [1111212,2232323,4435353....
// Time taken: 500ms

debug('This is a debug test!', [1, 2, 3], JSON.stringify(largefile));
// With process.env.DEBUG === undefined
// Output: <empty>
// Time taken: 500ms
               ^^^^^!!!!

With debug3

const debug = require('debug3')('http');

debug([1, 2, 3], () => JSON.stringify(largefile));
// With process.env.DEBUG === 'super-server:*'
// Output: **super-server:http** [1, 2, 3], {"large-json-file": [1111212,2232323,4435353....
// Time taken: 500ms

debug([1, 2, 3], () => JSON.stringify(largefile));
// With process.env.DEBUG === undefined
// Output: <empty>
// Time taken: 0ms
               ^^^ thats more like it!

Why debug3?

Because debug2 was taken :)

License

MIT. See LICENSE file