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

@waldronmatt/webpack-config

v3.0.1

Published

A shareable webpack configuration for projects.

Downloads

28

Readme

Webpack Config

A shareable webpack configuration with sensible defaults and extensible configs for assets.

Inspired by configuration practices found on survivejs.com.

Install

yarn add -D webpack webpack-merge webpack-cli @waldronmatt/webpack-config

Usage

package.json

"scripts": {
  "dev": "webpack --env development --config webpack.dev.js",
  "build": "webpack --env production --config webpack.prod.js"
}


webpack.dev.js

const { extendWebpackBaseConfig } = require('@waldronmatt/webpack-config');
const commonConfig = require('./webpack.common.js');

const developmentConfig = {
  // dev configs
};

module.exports = extendWebpackBaseConfig(commonConfig, developmentConfig);


webpack.prod.js

const { extendWebpackBaseConfig } = require('@waldronmatt/webpack-config');
const commonConfig = require('./webpack.common.js');

const productionConfig = {
  // prod configs
};

module.exports = extendWebpackBaseConfig(commonConfig, productionConfig);


webpack.common.js

  • Use isProduction to apply configs based on the environment.
  • Access Webpack's env variable.
  • Apply extensible base configs from @waldronmatt/webpack-config.
  • Include your own extensible configs using your own parts via const parts = require('./webpack.parts.js');.
  • Configs you set will take precedence if they overlap with @waldronmatt/webpack-config.
const { merge } = require('webpack-merge');
const { baseParts } = require('@waldronmatt/webpack-config');
const parts = require('./webpack.parts.js');

const commonConfig = (isProduction, env) => {
  // pass `isProduction` and Webpack's `env` variable into your parts file
  parts(isProduction, env);

  return merge([
    {
      entry: {
        main: './src/index.js',
      },
    },
    baseParts.loadJS({}),
    baseParts.setScriptOutputPath({}),
    baseParts.loadCSS({}),
    baseParts.setStyleOutputPath({}),
    // custom configs from your own `parts` file
    parts.loadHTMLPages({
      title: 'about',
    }),
  ]);
};

module.exports = commonConfig;


webpack.parts.js

Optionally set up your custom config parts to include in webpack.common.js.

const { MiniHtmlWebpackPlugin } = require('mini-html-webpack-plugin');

const parts = (isProduction, env) => {
  module.exports.loadHTMLPages = ({ title } = { title: 'MySite' }) => ({
    plugins: [
      new MiniHtmlWebpackPlugin({
        context: { title },
        publicPath: isProduction ? 'mydomain' : '/',
      }),
    ],
  });
};

module.exports = parts;

Options

You can load optional configs from this package into your own:

webpack.common.js

const { baseParts } = require('@waldronmatt/webpack-config');
  • baseParts.loadCSS({})
  • baseParts.loadSCSS({})
  • baseParts.setStyleOutputPath({})
  • baseParts.loadSourceMaps({})
  • baseParts.loadJS({})
  • baseParts.enableTypeChecking({})
  • baseParts.setScriptOutputPath({})
  • baseParts.loadImagesAsFiles({})
  • baseParts.loadImagesAsFilesOrInline({})
  • baseParts.loadFonts({})
  • baseParts.loadRawAssets({})

Note: See /src/webpack.parts.js for configuration options.

Loaders

  • esbuild-loader
  • fork-ts-checker-webpack-plugin
  • css-loader
  • postcss-loader
  • sass-loader
  • style-loader
  • mini-css-extract-plugin.loader
  • source-map-loader

Plugins

  • mini-css-extract-plugin
  • ESBuildMinifyPlugin

Included Dependencies

  • sass
  • typescript

Core Package Dependencies

  • webpack
  • webpack-merge

License

MIT