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-env-change

v1.0.1

Published

Change process.env.NODE_ENV in gulp scripts

Downloads

2

Readme

gulp-env-change

Change NODE_ENV in a gulp chain

why?

To change NODE_ENV for specific tasks in your build chain.

If using a single image for deployment over dev/staging/prod, building with NODE_ENV='production' might not be an acceptable solution, this plugin allows you switch NODE_ENV for specific tasks (such as minifying+uglifying a production version without requiring a separate build).

installation

$ npm install --save-dev gulp-env-change

#usage

import envChange from 'gulp-env-change';

gulp.task('foo', () => {
  return gulp.src('./src/*.js')
    .pipe(envChange({environment: 'production'}) // switch NODE_ENV to production for uglify
      .pipe(rename({suffix: '.min'})
      .pipe(uglifyjs())
    .pipe(envChange({environment: 'reset'}) // switch NODE_ENV back to previous setting
    .pipe(gulp.dest('./target/'))
});