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-micro-cluster

v1.1.1

Published

multiple webpack instances work together

Downloads

35

Readme

webpack-micro-cluster

multiple webpack instances working together

Build Status GitHub repo size

Install

npm install --save-dev webpack-micro-cluster

Introduction

webpack-micro-cluster is a webpack plugin at webpack-dev-server environment. In the large amount of code single project, debugging performance optimization can be given a less costly solution.It can also be used in dev support of the migration process from single project to micro services.

Usage

// Master Node webpack.config.js

module.exports = {
 // ....
  
  plugins: [
   //...
    new Master({
      masterId: 'demo', // The Name of Master
      injected: [`var __WORKERS__ = window.__WORKERS__ = window.__WORKERS__ || {};`]
    })
  ]
}

// `injected` will be injected into the top of main context 

// Worker Node webpack.config.js
module.exports = {
  entry: {
    index: './index.js'
  },
  
  output: {
 		// ....
    libraryTarget: 'assign',  
    libraryExport: 'default',
    library: ['__WORKERS__', 'worker0'] 
  },
  
  plugins: [
   //...
    new Worker({
      masterId: 'demo', // The Name of Master
      workerId: 'worker0', // The Name of Current Worker Node,
      entry : "index" // default is "index" 
    })
  ]
}

API

Master

  • masterId : string

    the name of master node, provided for configuration file use.it also provides a dist for worker nodes

  • injected? : Array<string | Loader | [string | Loader, IInjectOptions]>

    will be injected into the top of main context . you can put some pre-processing logic .

    1. string : injected Content
    2. Loader : () => string
    3. IInjectOptions : webpack-inject-plugin `s options

Worker

  • masterId: string

    point to a master node

  • workerId : string

    the name of current worker node, you must ensure that the node name is unique under the same masterId ,because this value is the basis for the master node to perform the update operation.

  • entry?: string // default : "index"

    the entry represents the reference file name of the output performed by the current worker node, which is sent to the master node as the source of the updated file contents.

Features

  • ability to make multiple webpack instances working together

  • automatically update the contents of the master node when the worker nodes start and stop

  • quick response to recompile

  • without using any hacks to interfere with the webpack execution logic, you can refer directly to an existing webpack project