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-config-organizer

v0.3.1

Published

A helper for separating concerns related to webpack environment and preset config files

Downloads

33

Readme

MIT License Publish package to npm Build & Test CodeFactor

Webpack config organizer

Webpack helper to organize your configurations separating them by concerns. This package achieves that by using two scope of files: presets and environments. Thereof you can define two types of files and both of them relies upon webpack --env CLI option. Environment configuration files help you define a config for different kinds of environments (dev, prod, debug, ci, and so on), while presets help you create predefined settings which help you to fast test a new build or just use make it cleaner.

Installation

Install using npm:

  npm install --save-dev webpack-config-organizer

Usage

First, you need to define a search path for your configs. You can use cosmiconfig to tell where to look for (package.json or .webpack-config-organizerrc.json):

// package.json
{
	"webpack-config-organizer": {
		"base": "path/to/your/env-and-presets-configs/", // relative to your project folder
		"environment": {
			"path": "/base/path/to/environment/configs/", // relative to "base"
			"prefix": "env-files-prefix"
		},
		"presets": {
			"path": "/base/path/to/presets/configs/", // relative to "base"
			"prefix": "presets-prefix"
		}
	}
}

On your webpack.config.js file use the tool to load your configurations:

const { organizer } = require("webpack-config-organizer")

module.exports = organizer({
    entry: "./src/main.js"
    output: {
        file: "[name].js"
    }
})

Using default presets

You can define default presets which are always loaded

const { organizer } = require("webpack-config-organizer")

module.exports = organizer(["typescript", "analyzer"], {
    entry: "./src/main.js"
    output: {
        file: "[name].js"
    }
})

Examples

Suppose you have the following configurations:

$ cd project-folder
$ ls build-tools/*

  build-tools/env:
  webpack.development.js
  webpack.debug.js
  webpack.ci.js

  build-tools/presets:
  webpack.typescript.js
  webpack.analyzer.js

and the given search parameters:

// package.json
{
	"webpack-config-organizer": {
		"base": "build-tools",
		"environment": {
			"path": "env",
			"prefix": "webpack."
		},
		"presets": {
			"path": "presets",
			"prefix": "webpack."
		}
	}
}

To load typescript and analyzer presets and debug environment:

$ npx webpack --env mode=debug --env.presets.typescript --env.presets.analyzer

Default presets

If you don't want to specify presets using the CLI, you can load them no matter what:

const { organizer } = require("webpack-config-organizer")

module.exports = organizer(["typescript", "analyzer"], {
    entry: "./src/main.js"
    output: {
        file: "[name].js"
    }
})

typescript and analzer presets will be always loaded:

$ npx webpack

Run Locally

Clone the project

  git clone https://github.com/pherval/webpack-config-organizer

Go to the project directory

  cd webpack-config-organizer

Install dependencies

  npm install

Build the application optionally

  npm run build

Running Tests

To run tests, run the following command

  npm t

License

MIT