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

babel-plugin-remove-debug

v0.0.4

Published

Removes usages of the npm debug module

Downloads

215

Readme

babel-plugin-remove-debug

Removes usage of the popular debug library from code.

The following:

import foo from './foo';
import Debug from 'debug';
const debug = Debug('bar');

function bar(x) {
   debug('Doing something');
   foo(1, x);
}

will be transformed into:

import foo from './foo';

function bar(x) {
   foo(1, x);
}

This is useful to help save on bundle size and be sure that log messages aren't being shown to clients. It also makes it safe to leave in potentially-expensive logging messages for development and be confident they won't impact production runtimes at all.

Limitations

  • Will only work if debug is imported with ES6 import syntax. require('debug') is not supported.
  • Doesn't do any particularly advanced flow analysis -- if you do weird things like aliasing the value you import from debug, the best we can do is replace the import with a dummy assignment instead of totally removing it. (eg import Debug from 'debug'; const x = Debug; x('hi')('yo'); will be safely neutered but won't be reduced to nothing even though it theoretically could. Notably, all the arguments in the x('hi')('yo') line will still be evaluated.)

Options

A typical setup

{
    "plugins": ["babel-plugin-remove-debug"]
}

By default this will apply to all import of 'debug'. If you are using a compatible but differently named package, or otherwise have the import name aliased, you can specify that using the libraries option. It accepts an array of regular expressions (as strings). For example:

{
    "plugins": [
        ["babel-plugin-remove-debug", {
           "libraries": [
             "^debug$",
             "^@mycompany/debug-fork-(1|2|3)$"
           ]
        }]
    ]
}