NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #3298 most downloaded on npm
Fix broken node modules with no fuss
Last release 1 years ago
29 Sep 2025
Ships unpredictably
gaps range from 8 days to 1.7 years
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
98 releases · first in 2017
Nothing published for this version
Fix idempotency regression. See #39
Add --reverse option for patch application. See #37
--reverse option for patch application. See #37One column per quarter.
Recommend postinstall-prepare in README for yarn compatibility
Ignore all package.json files by default
Fix bug where patch-package was complaining about failing when it had, in fact, succeeded. See #31
Remove git headers from patch files to prevent git from thinking files are part of the index
Change the way patch files are re-written when the project root dir is not the same as the git root dir.
Nothing published for this version
- Update README
Ignore end-of-line whitespace when creating and applying patch files
Add support for filtering particular paths
Ensure use of unix-style paths everywhere
Fix description of a hunk in error message
Don't use git apply with --unsafe-paths since it is useless.
git apply with --unsafe-paths since it is useless.- Fix typo in error message
Revert previous fix and suggest editing .gitattributes as an alternative
- Fix CRLF handling on Windows
- Add npm shrinkwrap support
Use posix paths and line separators even on windows, for git's sake.
Resolve paths in patch files for situations where the git root is not the same as the app root.
Pass --unsafe-paths option to git apply to let it work on arbitrary file paths (i.e. files which are not in a git repo or files which are outside of t
git apply to let it work on arbitrary file
paths (i.e. files which are not in a git repo or files which are outside of
the working directory)Add progress reporting during patch making
Use cross-spawn for spawning child processes
Windows fixes:
cross-spawn for spawning child processesgit apply for applying patches, rather than patchContribution by @ashmind
Use fs-extra to copy files instead of the cp shell command, which doesn't work on Windows
fs-extra to copy files instead of the cp shell command, which doesn't
work on WindowsUse + instead of : in patch file names because : is illegal on Windows.
+ instead of : in patch file names because : is illegal on Windows.Make update-notifier message show local install
Add update-notifier to notify users of patch-package updates
Add support for scoped packages
Make yarn patching a cli option, off by default
Improve error messages
Improve error messages
Reduce yarn error to a warning
Reduce yarn error to a warning
Merge pull request #4 from jirutka/yarn 98fd6d6
https://github.com/ds300/patch-package/compare/d5242cc74d47fb9d8aef688ece8aa8aa0dbaec72...v2.0.0
Moving fast and breaking things. It turns out yarn doesn't run the prepare hook after removing a package, so we use patch-package to patch a local version of yarn. I'm not proud of this. Probably wouldn't have released this in the first place if I had known that yarn didn't have all the right hooks. Oh well. Now I have a reason to contribute to Yarn I guess.
Fix patch creation logic around nested node_modules
Enable picking up changes in nested node_modules folders.
Fix bug that made exit code 1 regardless of success or failure.
Add nice colorful log messages.
Initial broken release
Initial broken release
Your coding agent can read these notes before it upgrades. Set up the MCP server →