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 🙏

© 2024 – Pkg Stats / Ryan Hefner

babel-plugin-debug

v1.0.1

Published

Babel plugin that replaces the "debug" keyword with an condition for dev- and debug-specific code.

Downloads

6

Readme

babel-plugin-debug

Build Status npm Code Climate
NPM

this plugin replaces debug-statements with environment related if-statements which can be garbage-collected by minifiers

how it works

example:

debug: {
    // log something for development
}

will be converted to

if(process.env.DEBUG === 'true') {
    // log something for development
}

so, when the transpiled code is run, the code block will only be executed when run the environment variable DEBUG is set.

use with webpack

when used with webpack you can use the webpack.DefinePlugin to pass the DEBUG variable

plugins: [
    new webpack.DefinePlugin({
      'process.env': {
        'DEBUG': `"${process.env.DEBUG}"`
      }
    })
  ]
  

example

debug: {
    // log something for development
}

and webpack is run with

DEBUG=true webpack

this yields the following output:

if(true) {
    // log something for development
}

which then can be collected by minifiers


when webpack is run with

webpack

then this yields the following output

if(false) {
    // log something for development
}

where as then the whole block will be thrown to trash by minifiers

little extra: named debugs

sometimes you want to give scopes to your debug statements so you can do the following:

debug_myblock: {
    // some debug
}

then you can enable these with the following

DEBUG=myblock webpack

this generates the following JS

if(process.env.DEBUG === 'true' || process.env.DEBUG === 'myblock') {

}

NOTE: all scopes are enabled when used with DEBUG=true (obviously)