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

node-module-patch-source-loader

v1.0.1

Published

patch node module source code during webpack compile time

Downloads

2

Readme

node-module-patch-source-loader

Patch node module source code during webpack compiling time.

Sometimes, when you find an issue in node module package A, but in fact the root is in its dependency package B.

To fix the issue, you need to raise a pull request to package B and then hope package A can be re-published using the new version of package B.

Or you can use yarn resolutions to force package A to use the new version package B.

Anyway, this may take some time.

During development, you can use this source loader to fix the issue by replacing package B source code with the right one in webpack runtime.

Install

Use npm install node-module-patch-source-loader --save-dev or yarn add node-module-patch-source-loader --dev.

How to use

In webpack.config.js file, add a new loader:

    const createNodeModulePatchSourceLoader = require('node-module-patch-source-loader');

    ...
    module: {
        rules: [
            createNodeModulePatchSourceLoader('source-code.esm.js', [
              {
                code: /var current = node\.parentNode;/g,
                newCode: 'var current = node && node.parentNode;'
              }
              {
                code: 'var target = event.target;',
                newCode: 'var target = (event.composedPath && event.composedPath().shift()) || event.target;'
              }
            ], 'node-module-package-name'),
            ...
        ]
  ...

The code, which matches the conditions in the array in node_moudles 'node-module-package-name' package 'source-code.esm.js' file, will be replaced by the newCode.

You have to know the source code file name in the package.

The replacement of the code needs to follow this format:

{
  code: the code to be replaced or RegEx of the code to be replaced,
  newCode: The new code that will be used
}