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-koa-stats-exposer

v1.0.0

Published

find webpack bundle paths and expose them to your webserver

Downloads

3

Readme

webpack stats exposer

expose the right webpack bundle paths to koa.

exports

  • getBundlePaths
    • ({statsFilePath}) => [::string]
    • finds the paths to javascript files by inspecting a webpack stats file:
  • buildExposeBundlePathsKoaMiddleware
    • ({defaultBundlePaths, ctxPropertyName}) => (ctx, next) => ::Promise
    • middleware builder that exposes the js paths on ctx. The script paths are extracted from ctx.state.webpackStats if it is set, whichis useful for automatically using the script paths in conjunction with webpack-dev-middleware.

usage

build script:

webpack --profile --json > webpack-stats.json

koa server definition:

import Koa from 'koa';
import {
  getScriptPaths,
  buildExposeAssetPathsKoaMiddleware,
} from 'webpack-stats-explorer';
const builtBundlePaths = getScriptPaths({statsFilePath: 'webpack-stats.json'})
const app = new Koa();
if (process.env.NODE_ENV !== 'production') {
  app.use(koaWebpack({compiler})) // compiler is an instance of webpack(config)
}
app.use(buildExposeAssetPathsKoaMiddleware({
  defaultBundlePaths: builtBundlePaths,
  ctxPropertyName: 'jsPaths'
});
app.use(ctx => {
  ctx.body = `
    <!doctype HTML>
    <html>
      <head>
        <title>hello world</title>
      </head>
      <body>
      ${ctx.bundlePaths
        .map(bundlePath => `<script type='application/json' src='${bundlePath}' ></script>`)
        .join('\n')
      }
      </body>
    </html>
  `;
})

In the example app above, ctx.bundlePaths will be set to the paths in the stats object at ctx.state.webpackStats when present (i.e. when NODE_ENV !== production and koaWebpack is used), otherwise the bundle paths will be found in webpack-stats.json`. So, when koa-webpack is used, the bundles that it produces will be exposed on the page, otherwise, the bundles built by the build script will be used.