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

total-config-webpack-plugin

v1.0.0

Published

Webpack Plugin for combining config files into one

Readme

Table of Contents

Motivation

In some projects, I wind up with tons of ***.config.js files, for example babel.config.js, jest.config.js, postcss.config.js, etc. Since they all start with different names, these files wind up scattered throughout my file tree, hard to visually find, and add a lot of clutter for files which rarely change. This plugin allows you to combine those files into one.

Who is this for?

This is for you if you have multiple configuration files, especially if they don't change very often.

It is not for you if you only have one config file or if you're not using webpack.

Features

  • Combine all ***.config.js files into a single total.config.js file
  • UPCOMING: Specify different filepaths as alternatives to ***.config.js
  • UPCOMING: Choose between JS and JSON output for each config file

Usage

Note: If you use this plugin and also include the config files, the files will be deleted and overwritten by the plugin. Do NOT try to put your webpack config info into your total.config.js file

  1. Install: yarn add total-config-webpack-plugin

  2. In your webpack config, add this plugin:

const TotalConfigPlugin = require('../total-config-plugin/dist/cjs')

plugins: [
  ...
  new TotalConfigPlugin({}),
  ...
]
  1. Create a file in the same directory as your webpack config, and call it total.config.js. Here's an example:
module.exports = {
    test: {
        message: "Hello world!"
    },
    babel: {
      presets: ['@babel/preset-env']
    }
}

This will generate two temporary config files at build-time, test.config.js and babel.config.js, which will export the config objects given in the total config respectively.