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

webpack-plugin-istanbul

v1.0.3

Published

Minimal Webpack5 plugin for instrumenting code coverage using istanbul

Readme

Getting started

Install the library:

yarn add webpack-plugin-istanbul -D

How it works

You have the option to choose between a plugin and a loader to instrument your code for coverage. The plugin might be a better option if you are using a test runner that does not support loaders. The loader is a better option if you are feeling the plugin is too slow to handle.

The plugin is using processAssets with the stage of PROCESS_ASSETS_STAGE_ADDITIONS to read and update code, while the loader reads the code directly through webpack's loading mechanism.

Initially, the plugin/loader will createInstrumenter from the istanbul-lib-instrument package.

Both the plugin and the loader use the same configuration options and pass them along to the createTestExclude method. See the TestExclude.

Afterwards, will check if the requested file shouldInstrument and if so, it will be passed to instrumentSync method to finalize the instrumentation process.

To ensure your code is properly instrumented, you can check the __coverage__ variable in your browser's console.

Configuration

For the current time being, the following options are supported:

include?: string | string[]; // glob strings
exclude?: string | string[]; // glob strings
extension?: string | string[]; // dot file extensiosn (e.g. '.js', '.ts', ...etc)
cwd?: string;   // process.cwd() by default

Plugin Example

const { WebpackPluginIstanbul } = require("webpack-plugin-istanbul");

module.exports = {
  plugins: [
    new WebpackPluginIstanbul({
      include: ["src/**/*.js"],
      exclude: ["src/**/*.spec.js"],
      extension: [".js"],
      cwd: process.cwd(),
    }),
  ],
};

Loader Example

module.exports = {
  module: {
    rules: [
      {
        test: /\.(js|ts)$/,
        exclude: /node_modules/,
        use: {
          loader: "webpack-plugin-istanbul/loader",
          options: {
            include: ["src/**/*.js"],
            exclude: ["src/**/*.spec.js"],
            extension: [".js"],
            cwd: process.cwd(),
          },
        },
      },
    ],
  },
};

Credit

This plugin is based on the work of vite-plugin-istanbul by ifaxity. The plugin was originally created to work with Vite, but I wanted to use it with webpack. I decided to create a new plugin instead of forking the original because I wanted to make some changes to the API and the way the plugin works.