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

webpack-module-flavour-plugin

v0.0.2

Published

Webpack plugin that can at build time pick one of multiple versions of some module

Downloads

25

Readme

Webpack plugin that can at compile time decide which one of multiple flavours of required modules to use.

What is it

It is a plugin for webpack's resolver. It allows you to specify multiple flavours of same module. Then when you require it, only flavour specified in your webpack config will be picked.

  • works with loaders
  • works with node_modules or web_modules or whatever
  • doesn't work with contexts

Example

Let's say you want to require one of two flavours of popup component on mobile and desktop versions of your web application.

You'll have to do three things to achieve that.

First: name flavoured modules by the following scheme <module-name>.<flavour>.<extension>


    /root
     |-/flavoured-popup
     |  |-popup.mobile.js
     |  |-popup.desktop.js
     |-common-module.js

Second: configure webpack using array of configurations.

You'll have to specify different flavour for each configuration.

Also you'll be able to use "[flavour]" in output.filename


var path = require('path');
var ModuleFlavourPlugin = require('webpack-module-flavour-plugin');

var commonConfig = {
    entry: './entry-point.js',
    context: path.join(__dirname, 'src'),
    output: {
        path: path.join(__dirname, 'build'),
        filename: '[name].[flavour].js'
    },
    plugins: [
        new ModuleFlavourPlugin()
    ]
};

var MobileConfig = Object.assign({}, commonConfig, {
    flavour: 'mobile'
});
var DesktopConfig = Object.assign({}, commonConfig, {
    flavour: 'desktop'
});

module.exports = [MobileConfig, DesktopConfig];

Third: require it by <module-name>:


    var Popup = require('./flavoured-popup/popup');

Voila!

There is nothing else to say, really...