Question 1

How to set up patch-package with Docker?

Accepted Answer

Copy patch files before running npm install in your Dockerfile, and adjust .npmrc if you encounter working directory errors. The README provides specific steps to ensure patches apply during image builds.

Question 2

patch-package vs forking: which is better?

Accepted Answer

Patch-package is best for quick, temporary fixes shared via version control, while forking is better for major changes or upstream contributions. The README advises forking for consequential changes and patch-package for band-aid solutions.

Question 3

How to handle patch conflicts when updating a package?

Accepted Answer

If a patch fails after an update, manually review and update the patch file using patch-package with --partial for errors. The README notes that patches may need revalidation when dependencies change.

Question 4

Can I use patch-package with pnpm?

Accepted Answer

No, pnpm has native patching via pnpm patch, so patch-package is unnecessary. The README explicitly states that pnpm users should use their built-in tool instead.

Question 5

How to create a dev-only patch?

Accepted Answer

Rename the patch file with a .dev extension, e.g., package+version.dev.patch, to ignore it in production when NODE_ENV=production. The README details this for transitive dev dependencies.

Question 6

What happens if I forget to reinstall node_modules when switching branches?

Accepted Answer

You might end up with inconsistent patches applied, causing errors. The README warns this is a common pitfall and suggests being diligent about reinstallation.

patch-package

What is patch-package?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions