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

node_modules_patches

v0.2.1

Published

Many times you'd want to change code in `node_modules` libraries. Even if you've made a pull request to the original author's library it still takes some time.

Downloads

8

Readme

node_modules_patches

Many times you'd want to change code in node_modules libraries. Even if you've made a pull request to the original author's library it still takes some time.

To ensure you changes are always applied when you fresh install dependencies you should store the affected/changed files separately, in node_modules_patches

For example I have made some changes in isomorphic-webpack\dist\factories\createIsomorphicWebpack.js and style-loader\addStyles.js and I've stored these files in node_modules_patches

node_modules_patches will copy these files onto node_modules directory in their respective location and also display a diff of files copied, or show "skipped" if diff doesn't exist.

The diff lets you know if with an updated version you no longer need to be patching the file or if there's been too many changes since you created the patch file and might need to rebase your patch again.

Install

npm i node_modules_patches

Usage

node_modules_patches [<patch dir eg. "node_modules_patches" (default)>]

Example

$ tree
project
├───files
│   …
├───node_modules_patches // node modules patches folder
│   ├───isomorphic-webpack
│   │   └───dist
│   │       └───factories
│   │           └───createIsomorphicWebpack.js // < copies this
│   └───style-loader
│       ├───index.js
│       └───addStyles.js // < and this
│
├───node_modules
│   …
│   ├───isomorphic-webpack
│   │   ├───dist
│   │   …   ├───factories
│   │       │   └───createIsomorphicWebpack.js // < to here
│   │       ├───schemas
│   │       ├───utilities
│   │       …
│   …
│   ├───style-loader
│   …   ├───.github
│       ├───addStyles.js // < and to here, respectively
│       ├───addStyleUrl.js
│       ├───index.js
…       …
$ node_modules_patches
Copied: isomorphic-webpack\dist\factories\createIsomorphicWebpack.js
  - var relativeEntryScriptPath = './' + _path2.default.relative(webpackConfiguration.context, require.resolve(entryScriptPath));
  + var relativeEntryScriptPath = './' + _path2.default.relative(webpackConfiguration.context, require.resolve(entryScriptPath)).replace(/[/\\]+/g, '/');
Copied: style-loader\addStyles.js
  - return /msie [6-9]\b/.test(self.navigator.userAgent.toLowerCase());
  + return /msie [6-9]\b/.test(window.navigator.userAgent.toLowerCase());
Skipped: style-loader\addStyles.js