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

v1.5.2

Published

Adds easy environment configuration and conditional piping to Gulp, based on NODE_ENV or parameters with yargs.

Downloads

1,661

Readme

gulp-environment

Adds easy environment configuration and conditional piping to Gulp, based on NODE_ENV or parameters via yargs.

with :purple_heart:, —@helloitsdan

Build Status

Usage

This module will load a list of available environments and try to figure out which one it's currently running in by looking at the env parameter first, falling back to the NODE_ENV environment variable if that doesn't exist, and then config.default last. These can be specified either by name directly, or by one of a few aliases. For example, development mode can be referenced as either development, dev, or local by default.

To run gulp in production mode using this module, specify your environment either via gulp --env=production or NODE_ENV=production gulp. Your gulp tasks will then be able to conditionally pipe plugins as follows...

Example

var gulp = require('gulp')
var env = require('gulp-environment')
var cleanCSS = require('gulp-clean-css')

gulp.task('minify-css', function() {
  return gulp.src([
    'assets/css/**/*.css'
  ])
    .pipe(
      env.if.production(cleanCSS()).else(neverRunThisOnLive())
    )
    .pipe(gulp.dest('web/assets/css/'))
})

Confguring environments

The module will first try to find a .gulpenvrc file from your current working directory. This should be a JSON file, formatted as follows:

{
  "environments": [
    {
      "name": "development",
      "aliases": [ "dev", "local" ]
    },
    ...
  ],

  "default": "development"
}

If the module cannot find a .gulpenvrc, it'll try and find the nearest package.json file and load config from the gulp-environment block. If neither of these are found, it'll use the default config specified in this module's .gulpenvrc.

API

Each of the methods below will be created for each of the environments defined in config.js—by default, this is development, qa, and production.

env.current

A getter/setter to access the current environment.

env.is.environment()

Returns a boolean representing whether or not the current environment is environment.

  var headers = env.is.qa() ? "QA" : "Live";

This function can also be accessed manually via env.is(environment)

env.if.environment(ifTrue)[.else(ifFalse)]

Returns ifTrue if the current environment is environment, otherwise returns a no-op. If the else chaining function is used, ifFalse will be returned when not in environment, otherwise ifTrue will be returned as normal.

  ...
  .pipe(
    env.if.production(cleanCSS()).else(neverRunThisOnLive())
  )
  ...

This function can also be accessed manually via env.if(environment, ifTrue[, ifFalse])

env.if.not.environment(ifFalse)

Returns ifFalse if the current environment is not environment, otherwise returns a no-op.

  ...
  .pipe(
    env.if.not.development(cleanCSS())
  )
  ...

This function can also be accessed manually via env.if.not(environment, ifFalse)