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-parts

v2.0.0

Published

Build your webpack config from composable and opinionated parts

Downloads

3

Readme

DEPRECATION NOTICE

webpack-parts was created before we knew about webpack-blocks which is the same idea but more established. Please use it instead as we will be porting to that and nuking webpack-parts.

webpack-parts

Build your webpack config from composable and opinionated parts.

Installation

$ yarn add --dev webpack-parts

Usage

Combine multiple webpack parts into a webpack config. A part is either an object, which will be merged in to the config, or it is a function that takes the config as it is and is expected to return a new version of the config. The parts are resolved in the order they are provided. There is a small base config that combine starts with that looks like this in production (chunkhash will be omitted if NODE_ENV !== 'production'):

{
  output: {
    filename: '[name].[chunkhash].js',
    chunkFilename: '[name].[chunkhash].js',
    publicPath: '/'
  }
}

Read the documentation to see the various parts that can be used.

Example

// webpack.config.js
const parts = require('webpack-parts')

module.exports = parts.combine(
  {
    entry: "app/index.js",
    output: {
      path: "build"
    }
  },
  parts.load.js(),
  parts.load.css(),
  parts.dev.sourceMaps(),
  parts.optimize.minimize()
)