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

gulp-if-env

v1.0.2

Published

Gulp plugin for environment-specific tasks

Downloads

220

Readme

gulp-if-env Build Status

A gulp plugin to conditionally run tasks for one or more environments.

Installation

Install the plugin using npm:

$ npm install gulp-if-env

Basic usage

Require in gulpfile.js

var ifEnv = require('gulp-if-env');

And use in your gulp tasks as such:

gulp.task('my-task', function () {
    return gulp
        .src('src/index.html')
        .pipe(ifEnv('production', myProductionTask()))
        .pipe(gulp.dest('public/'));
});

Want to run a task on all but one environment? Use not:

gulp.task('my-task', function () {
    return gulp
        .src('src/index.html')
        .pipe(ifEnv.not('development', nonDevelopmentTask()))
        .pipe(gulp.dest('public/'));
});

Or want to specify specific environments? No problem! Just use the includes function:

gulp.task('my-task', function () {
    return gulp
        .src('src/index.html')
        .pipe(ifEnv.includes('production', 'staging', myProductionTask()))
        .pipe(gulp.dest('public/'));
});

API

[main function]

There are three main interfaces to the main function:

ifEnv(); // Returns current environment
ifEnv('production'); // Returns `true` for production, `false` for other
ifEnv('production', myGulpTask()); // Returns `myGulpTask` stream for production, otherwise no-op

.not([environment], [gulpStream])

There are two main interfaces to the not() function:

ifEnv.not('production'); // Returns `true` in production, `false` for others
ifEnv.not('production', myGulpTask()); // Returns `myGulpTask` stream for production, otherwise no-op

.includes([environment1], [environment2], [...more...], [gulpStream])

There are two main interfaces to the includes() function:

ifEnv.includes('production', 'staging'); // Returns `true` in production and staging, `false` for others
ifEnv.includes('production', 'staging', myGulpTask()); // Returns `myGulpTask` stream for production and staging, otherwise no-op

.excludes([environment1], [environment2], [...more...], [gulpStream])

There are two main interfaces to the excludes() function:

ifEnv.excludes('production', 'staging'); // Returns `false` in production and staging, `true` for others
ifEnv.excludes('production', 'staging', myGulpTask()); // Returns no-op in production and staging, `myGulpTask` for others

.set(environment)

Sets a new environment if a change is required, or if your environment is specified somewhere other than NODE_ENV or as env CLI argument

ifEnv.set('staging');
ifEnv('production'); // Returns false
ifEnv('staging'); // Returns true

.reset()

Resets to default (NODE_ENV or env CLI argument)

ifEnv.set('staging');
ifEnv('staging'); // Returns true
ifEnv.reset();
ifEnv('staging'); // Returns false
ifEnv('development'); // Returns true

Issues/contribution

Feel free to create an issue or pull request if you see something amiss. Thanks!