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 🙏

© 2026 – Pkg Stats / Ryan Hefner

webpack-profiles

v1.0.0

Published

Profiles support for webpack module bundler

Readme

webpack-profiles

Profiles support for webpack module bundler. It allows you to define multiple configuration profiles in separated file and trigger them e.g. for different build types.

Installation

$ npm install webpack-profiles --save-dev

Define profiles

Profiles are defined in profiles.js file, placed in the root directory of project. Filename can be modified (see Configuration).

Sample profiles.js:

var webpack = require('webpack');
module.exports = {
    production: {
        vars: { //section with variables passed to webpack.DefinePlugin
            API_URL: "'http://my.api.com'"
        },
        config: { //section with config merged with main webpack config
            devtool: 'source-map',
            plugins: [
                new webpack.optimize.UglifyJsPlugin()
            ]
        }
    },
    dev: {
        activeByDefault: true, // profile will be triggered if no profiles passed via cmd or options
        vars: {
            API_URL: "'http://localhost:8080'"
        },
        config: {
            devtool: eval
        }
    },
    ...
};

Applying profiles

Profiles are applied by webpack-profiles helper function, i.e. webpackProfiles(webpackConfigObject, [options]):

webpack.config.js:

    
    var webpackProfiles = require('webpack-profiles');

    var config = {
        entry: {
            app: './index.js'
        },
        output: {
            ...
        },
        plugins: [
            ...
        ],
        ...
    };
    
    module.exports = webpackProfiles(config, {profilesFilename: 'name.js'});

Activating profiles

Profiles can be activated in 3 ways:

Configuration

Options

Options can be passed as second argument to webpack-profiles helper function:

    defaults: {
        profiles: '', //multiple profiles can be pased as 'profile1,profile2,...'
        profilesFilename: 'profiles.js',
        returnProfiles: false, //see description below
        extend: {
            isDeep: true,
            arrays: 'concat'
        }
    }

Webpack configuration is merged using extendify, additional options can be passed as extend (instead of inPlace, it's always true).

returnProfiles: if you set it to true, webpack-profiles helper function will return following object:

    {
        config: *merged webpack config*,
        profiles: *array with configuration of profiles, that was used in current build*
    }

It can be useful when you want to make some custom operations depending on triggered profiles.

Command line

Some options can be passed as cmd arguments, that way they override values from options object:

  • profiles, e.g. $ webpack --profiles=dev,profile1,profile2
  • profilesFilename, e.g. $ webpack --profilesFilename=webpack.profiles.js

Command line argument can be passed in format supported by yargs.