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

require-variant-webpack-plugin

v0.1.1

Published

Webpack plugin for custom require resolution

Downloads

3

Readme

Require Variant Plugin

The problem

Normally, if you want to require a different file (code or resources) depending on some conditions, like an environment variable, you have to write this kind of convoluted code:

var View = null;
if (process.env.DEV) {
    View = require('./view.dev'); // ./view.dev.js
}
else {
    View = require('./view'); // view.js
}

or

if (process.env.FANCY) {
    require('./styles_fancy.scss');
}
else {
    require('./styles.scss');
}

It's ok if you do it once but if you start heavily relying on it, it becomes a burden.

The solution

Use this plugin to allow webpack to resolve the file variant automatically. It allows, from a single codebase, to customize profoundly the output without awkward conditional code.

Disclaimer: the caveat is that the custom resolution hides the file you really compile in your project - it may be a source of confusion, so use with care.

### Install via npm:

npm install --save-dev require-variant-webpack-plugin

### Update your webpack config:

const RequireVariantPlugin = require('require-variant-webpack-plugin');

const isDev = process.env.DEV;
const isFancy = process.env.FANCY;

module.exports = {
  plugins: [
    new RequireVariantPlugin(['.js', '.jsx'], isDev ? '.dev' : null),
    new RequireVariantPlugin(['.scss'], isFancy ? '_fancy' : null)
  ]
};

The plugin simply hooks to the files resolver and, if a variant exists, modifies the resolved path.

Everything works as usual: loaders and features like hot-reload use the variant file as reference.

Usage

Run webpack with or without environment vars to select the variant:

# no variant
npm run build

const View = require('./view'); // view.js
require('./styles'); // styles.scss

# with variant
FANCY=true npm run dev

const View = require('./view'); // view.dev.js
require('./styles'); // styles_fancy.scss

API

new RequireVariantPlugin(extensions:string[], variantPostfix:string, includeNodeModules:boolean)
  • extensions: array of strings; file paths are matched to end with one of those,
  • variantPostfix: string; inserted before the extension in matched file paths,
  • includeNodeModules: boolean; normally node_module is ignored.