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

conditionalify

v1.1.0

Published

Browserify transform to remove code from a Browserify build using conditional comments.

Downloads

20

Readme

conditionalify

Browserify transform to remove code using conditional comments. Comments are evaluated using angular-expressions.

Installation

$ npm install --save-dev conditionalify

Usage

Given the Following script.js:

var data = require('data.json');

/* #if someValue === 'foo' */
var result = require('foo-parser')(data);
/* #endif */
/* #if someValue !== 'foo' */
var result = require('other-parser')(data);
/* #endif */

console.log(result);

And the Following Usage:

CLI

$ browserify script.js -o bundle.js \
  -t [ conditionalify --context [ --someValue foo ] ]

Node

var fs = require('fs');
var browserify = require('browserify');
browserify('./script.js')
    .transform('conditionalify', {
        context: {
            someValue: 'foo'
        }
    })
    .bundle()
    .pipe(fs.createWriteStream('bundle.js'));

The Following Output Would be Produced:

var data = require('data.json');

/* #if someValue === 'foo' */
var result = require('foo-parser')(data);
/* #endif */
/* #if someValue !== 'foo' */
/* #endif */

console.log(result);

Options

The following configuration options are available (and are all optional):

  • context (Object): An Object whose keys will be available as variables in the comment expressions
  • marker (String): The character to look for at the start of a comment (before if or endif)—defaults to #
  • ecmaVersion (Number): Version of ECMAScript to pass to acorn when parsing each module
  • exts (Array of Strings): A whitelist of file extensions (without the leading ".")—if a file does not have one of the extensions in the list, it will be ignored by conditionalify—defaults to ['js']

Options may be passed in via standard browserify ways:

$ browserify -t [ conditionalify --marker @ ]
browserify().transform('conditionalify', { marker: '@' });
var conditionalify = require('conditionalify');
browserify().transform(conditionalify, { marker: '@' });