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

@hungry/webpack-parallel

v0.2.2

Published

Dev friendly webpack builder and watcher

Downloads

3

Readme

Webpack parallel runner

Command line tool for running webpack multiple configurations written in typescript with watch ability.

Look and feel

clean-run

Install

# global yarn
yarn global @hungry/webpack-parallel

# global npm
npm install -g @hungry/webpack-parallel

# or as dependency
yarn add @hungry/webpack-parallel

Usage

webpack-parallel run --config your_config --fullReport

Config file

webpack-parallel expects array, single config or a Promise of config/s.

const myConfigs = [...] // array of webpack configs

// optional - if you'd see named configs instead of seeing indexes
export const configNames = ['friendly-config-name-1', 'friendly-config-name-2'] 

export default new Promise(...)
  .then(...) // do some clean up, any shared operations before build or watch
  .then(()) => myConfigs)

Supported commands

Run parallel webpack

Options:
  --version     Show version number                                    [boolean]
  --help        Show help                                              [boolean]
  --config                                     [string] [required] [default: ""]
  --cwd                                                            [default: ""]
  --workerFile                                                     [default: ""]
  --fullReport                                                  [default: false]
  --silent                                                      [default: false]
  --watch                                                       [default: false]

How to use it

It is used in conjunction with @hungry/webpack-parts - composable, typesafe webpack config, however it is not necessary.

Selling points

  • compatible with webpack watch
  • compatible with webpack-dev-server and hmr
  • reliable error handling
  • exposed separate command for yargs if you've got already your custom command line tree
  • full report activity - sorted by worker id report from stdin and stderr
  • can connect any worker - there is an utility class provided for communication and wrapper to run any config based on babel
  • full control over pipes and rendering phase - if you want to help me extend it

Motivation

There is couple of implementation of parallel building for webpack, however I wanted to provide something dev oriented with clear error reporting when there is spawned many of concurrent builds.