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-middware-2

v1.1.3

Published

Webpack middleware module

Downloads

15

Readme

#Webpack-middware npm David David ![GitHub tag](https://img.shields.io/github/tag/hinell/webpack-middware.svg?maxAge=2592000&style=flat-square&label=Github tag) JUMP TO: Class API | Configuration | Miscellaneous Server middleware that manages your webpack compilation when in development. This completely rewritten and heavily tested the webpack-dev-middleware brings a powerful support of multiple webpack configurations and some features enhancing basic functionality. See below.

$ npm i webpack-middware
$ npm i hinell/webpack-middware --production # latest version
var   compiler  = new Webpack(/* your configs, one or more.. */)
    , Middware  = require('webpack-middware')
    , app       = require('express')();
      app.use((middware = new Middware({
        compiler    : compiler, // compiler property is required!
        publickPath :'/public'  // by default '/'
      , headers     : {         // headers to be served to
        , 'Cache-control': 'max-age=0' // every client requiest
        , files :                      // or for specific file request
            {'vendor':{'Cache-control': 'max-age=3600'}}// headers are sent with response  when the name
                                                        // of any requested webpack output bundle
                                                        // matches for instance to the 'vendor' regexp
      , fs          : new require('memory-fs') // feel free to choose the file system
      , watch       : {}  // watch config
      })).middleware)     // ⚠ don't forget to provide the middleware callback to the .use()!
      app.listen(3000);
      // Miscellaneous
      middware.watching              // access watching, undefined in lazy mode (lazy option is specified)
      middware.watching.invalidate() // invalidate bundle
      middware.fs                    // file system access

API

var   middware = new Middware(compiler[, config]) // middware takes webpack compiler and optional config
var   middware = new Middware(config) // the compiler passed by the config property like {compiler: compiler}

middware.middleware - (req,res,next) - server request listener (middleware)

Config

.compiler - webpack compiler instance, this option is required .fs - files system where compiled files are kept, by default it is equal to the require('fs') .headers - {header: value} - serve headers along the response on each request to the webpack output bundle picked by name .headers.files - {filename:{header: value}} - the same as .headers but only for a particular webpack output bundle .filename - String - filename on which request middware starts compilation (lazy mode required) .publicPath - String - by default '/' .lazy - Boolean - activate lazy mode so middware compiles bundle by request, false by default .error - Boolean - log errors, false by default .debug - Boolean - log debug info, false by default .quiet - Boolean - log no info about compilation, except errors and debug, false by default

Miscellaneous

Rest of options can be found here. Webpack multiple configurations.