diff --git a/docs/changing-rules.html b/docs/changing-rules.html
index 2e636dfe9b..9065a89497 100755
--- a/docs/changing-rules.html
+++ b/docs/changing-rules.html
@@ -187,9 +187,14 @@ <h1 id="making-changes-to-rules_nodejs">Making changes to rules_nodejs</h1>
 
 <h2 id="patching-the-npm-packages">Patching the npm packages</h2>
 
-<p>The pattern we use most commonly is to add a <code class="language-plaintext highlighter-rouge">postinstall</code> hook to your <code class="language-plaintext highlighter-rouge">package.json</code> that patches files after they’ve been fetched from npm.</p>
-
-<p>See <code class="language-plaintext highlighter-rouge">/tools/postinstall-patches.js</code> in the <a href="https://github.com/angular/angular/tree/master/tools/postinstall-patches.js">Angular repo</a> for an example.</p>
+<p>The pattern we use most commonly is to use <a href="https://www.npmjs.com/package/patch-package">patch-package</a>. To store your local changes to the npm packages follow the steps:</p>
+
+<ol>
+  <li><code class="language-plaintext highlighter-rouge">npm i -D patch-package</code></li>
+  <li>Edit the target package in your <code class="language-plaintext highlighter-rouge">node_modules</code></li>
+  <li>Run <code class="language-plaintext highlighter-rouge">npx patch-package &lt;npm package&gt;</code>. This will store the patch in the <code class="language-plaintext highlighter-rouge">patches/</code> directory in the root of the workspace</li>
+  <li>Add <code class="language-plaintext highlighter-rouge">"postinstall": "patch-package"</code> to the <code class="language-plaintext highlighter-rouge">package.json</code> in your repo to apply the patches when building dependencies (aka at <code class="language-plaintext highlighter-rouge">npm install</code>)</li>
+</ol>
 
 <h2 id="patching-the-built-in-release">Patching the built-in release</h2>
 
diff --git a/docs/changing-rules.md b/docs/changing-rules.md
index 00a66b81c6..9824d19772 100644
--- a/docs/changing-rules.md
+++ b/docs/changing-rules.md
@@ -16,11 +16,14 @@ If you have a small change, it's easiest to just patch the distributed artifacts
 
 ## Patching the npm packages
 
-The pattern we use most commonly is to add a `postinstall` hook to your `package.json` that patches files after they've been fetched from npm.
+The pattern we use most commonly is to use [patch-package]. To store your local changes to the npm packages follow the steps:
 
-See `/tools/postinstall-patches.js` in the [Angular repo] for an example.
+1. `npm i -D patch-package`
+1. Edit the target package in your `node_modules`
+1. Run `npx patch-package <npm package>`. This will store the patch in the `patches/` directory in the root of the workspace
+1. Add `"postinstall": "patch-package"` to the `package.json` in your repo to apply the patches when building dependencies (aka at `npm install`)
 
-[Angular repo]: https://github.com/angular/angular/tree/master/tools/postinstall-patches.js
+[patch-package]: https://www.npmjs.com/package/patch-package
 
 ## Patching the built-in release