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 🙏

© 2026 – Pkg Stats / Ryan Hefner

runtime-package-generator-webpack-plugin

v1.0.3

Published

Moves Node dependencies into builds if they need to be separate for some reason. Allows for external runtime dependencies.

Readme

Runtime Package Generator

The main use of this plugin is to keep node dependencies separate from a server bundle at runtime. This might be for file size, security or obscure dependencies that do not play well with Webpacks loading mechanisms.

This Webpack plugin will allow you to generate a package.json dynamically for your build to automatically keep a specific set of modules that you want external or excluded from your bundle. It will let you define what dependencies to keep and generate a new package.json in your build folder to be used with npm for installing modules separately to your bundle(s).

Installation

  npm install runtime-package-generator-webpack-plugin --save-dev

Usage

The plugin must be used in conjunction with the nodeExternals feature, which will ignore a require (i.e. Webpack will not resolve it), like so:

  const nodeExternals = require('webpack-node-externals')
  const RuntimePackagePlugin = require('runtime-package-generator-webpack-plugin')
  const runtimeDependencies = ['dependency-1', 'dependency-2']

  {
    // ... config
    plugins: [
      new RuntimePackagePlugin({
        requiredAtRuntime: runtimeDependencies,

        // optional target directory. default: 'build/package.json'
        dest: 'build/server',

        // optional json format. These are defaults
        jsonFormat: {
          type: 'spaces',
          size: 2
        }
      })
    ],
    externals: [
      nodeExternals({
        whitelist: runtimeDependencies
      })
    ]
  }

You might wish to combine this with a postbuild task to keep everything automatic. This would cd into the target directory of your new package.json the plugin created and automatically run an npm install to get those separate node dependencies in there. This is out of the scope of what this plugin should deliver, hence it is recommended to do such a task like the below snippet.

  "prebuild": "rimraf build",
  "build": "NODE_ENV=production webpack --config webpack.config.js",
  "postbuild": "cd build/server && npm install"