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

environmentally

v0.1.3

Published

Create an environment-driven webpack.config.js

Downloads

2

Readme

Environmentally npm version npm downloads

Create an environment-driven webpack.config.js

Table of Contents

Installation

yarn add -D environmentally

Introduction

This is a tool that simplifies the creation of webpack configurations that are sensitive to the environment. This is especially useful when it's difficult to switch between development and production organically.

Usage

Just wrap your webpack config using Environmentally as follows:

Example #1
const Environmentally = require('environmentally');

module.exports = Environmentally(({ DEVELOPMENT, PRODUCTION }) => {
    return {
        plugins: [
            PRODUCTION ? new ProductionPlugin : new DevelopmentPlugin
        ]
    }
})

Read more about Helpers.

Example #2
const Environmentally = require('environmentally');
const When = require('environmentally/when');

module.exports = Environmentally(({ DEVELOPMENT, PRODUCTION }) => {
    return {
        plugins: [
            When({
                [PRODUCTION]: new ProductionPlugin,
                [DEVELOPMENT]: new DevelopmentPlugin,
            })
        ]
    }
})

Read more about Helpers.

Example #3
const Environmentally = require('environmentally');

module.exports = Environmentally(({ DEVELOPMENT, PRODUCTION }) => {
    if (DEVELOPMENT) {
        return require('./webpack.dev.js');
    }

    if (PRODUCTION) {
        return require('./webpack.prod.js');
    }
})
Example #4
const Environmentally = require('environmentally');

module.exports = Environmentally(({ ENV }) => {
    return require('./webpack.' + ENV + '.js')
});

API

Environmentally

const Environmentally = require('environmentally');

module.exports = Environmentally(({ DEVELOPMENT, PRODUCTION, ENV, MODE, WEBPACK_ARGV }) => {
    // ...
});

Below there's a table explaining how the values are determined:

| COMMAND | DEVELOPMENT | PRODUCTION | MODE | ENV | - | -: | -: | -: | -: | webpack -d | true | false | development | development | webpack -p | false | true | production | production | webpack --mode development | true | false | development | development | webpack --mode production | false | true | production | production | webpack -p --env production2 | false | true | production | production2 | webpack -d --env development2 | true | false | development | development2

Helpers

The following helpers work well with Environmentally:

  • Ternary operator (imperative)
    true ? 'foo' : 'bar' // === 'foo'
  • Binary operator (imperative)
    true && 'baz' // === 'baz'
  • When (declarative)
const When = require('environmentally/when');

When({
    [true]: 'corge',
    [false]: 'grault',
}) // === 'corge'

Interoperability

Environmentally works well with Babel (BABEL_ENV) and Node (NODE_ENV).

Support

Please open an issue for support.

Contributing

Please contribute using Github Flow. Create a branch, add commits, and open a pull request.