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-preprocessor

v0.0.5

Published

Used to transform preprocessor directives

Downloads

780

Readme

npm Node Downloads License Build Status English | 中文

Installation

yarn add -D babel-plugin-preprocessor

or

npm install -D babel-plugin-preprocessor

Options

interface PluginOptions {
  symbols: Record<string, any>;
  directives: Record<string, boolean>;
}

Set plugin options in babel configuration file:

{
  "plugins": [
    ...
    ["preprocessor", {
      "symbols": { "IS_BROWSER": true },
      "directives": { "DEBUG": true }
    }]
  ]
}

Usage

Build-in Directives

Before using #if / #else / #elseif (alias: #elif) / #endif build-in Directives, you need to configure the symbols option in the babel configuration file.

// #if IS_BROWSER
console.log('This is browser');
// #else
console.log('It\\'s unknown');
// #endif

If IS_BROWSER is truthy, console.log ('It\\'s unknown'); will be deleted and vice versa.

Complex use case

Use the symbols parameter like variable:

{
  "plugins": [
    ["preprocessor", { "symbols": { "IE": 8, "UA": "Chrome" } }]
  ]
}
// #if (IE > 8 && IE < 12) || UA.startsWith('Chrome')
console.log('Support HTML5');
// #else
console.log('HTML5 is not supported'); // This line will be deleted
// #endif

Custom Directives

By configuring the directives option to implement custom directives:

// #debug
console.log('debug message');

If debug is falsy, console.log will be deleted.

Note that the custom directive only affects its next line, which means:

// #debug
console.log('debug message'); // This line will be omitted
const a = ''; // This line will be retained

Compatible webpack-preprocessor-loader

This plugin is inspired by webpack-preprocessor-loader, Therefore, you can safely use its built-in directives:

// #!if IS_BROWSER
console.log('This is browser');
// #!else
console.log('It\\'s unknown');
// #!endifWW

If you use its #!debug directive, please configure directives option, If you also use its verbose option, then you need to configure the symbols option according to the usage.

Typescript

To suppress the error, a tricky way is simply adding // @ts-ignore before all declarations:

// #if ENV = 'develop'
// @ts-ignore
const foo = 1;
// #else
// @ts-ignore
const foo = -1;
// #endif

JSX

Since version 0.0.2, JSX directives have been fully supported:

import React from 'react';
import ErrorBoundary from './boundary';

export default () => {
  return (
    /* #if IS_BROWSER */
    <ErrorBoundary fallback={() => <div>Fallback</div>}>
    {/* #endif */}
      <div>
        {/* #debug */}
        <span>This line should be deleted</span>
        Do something
      </div>
    {/* #if IS_BROWSER */} 
    </ErrorBoundary>
    /* #endif */  
  );
}

If a JSX element has a close tag, the directive to close the tag can be omitted:

import React from 'react';
import ErrorBoundary from './boundary';

export default () => {
  return (
    /* #if IS_BROWSER */
    <ErrorBoundary fallback={() => <div>Fallback</div>}>
    {/* #endif */}
      <div>
        {/* #debug */}
        <span>This line should be deleted</span>
        Do something
      </div>
    </ErrorBoundary>
  );
}

However, I suggest you keep it so that it is compatible with webpack-preprocessor-loader

Pay attention to the wrapping of elements when using JSX, otherwise there will be some unexpected results:

import React from 'react';
import ErrorBoundary from './boundary';

export default () => {
  return (
    /* #if IS_BROWSER */
    <ErrorBoundary fallback={() => <div>Fallback</div>}>
    {/* #endif */}
      {/* #debug */}
      <span>This line should be deleted</span>
      Do something
    {/* #if IS_BROWSER */} 
    </ErrorBoundary>
    /* #endif */  
  );
}

If IS_BROWSER is false and debug is true, then Do something line will be discarded.