Note:<p>I just recently got bit by degenerate behavior of this package in yarn 1.x, which I didn't have the option to upgrade due to usecase.<p>I ended up just settling on using patch from GNU coreutils to apply the diffs.<p>The core of the degenerate behavior was that yarn 1.x does not have an option to not run builds after installs invocations, and if you're trying to uninstall postinstall or remove patch-package from a dist, a yarn remove will remove the package from node_modules, but will not deregister the lifecycle hook of the running NodeJS session, leading to chicken egg frustration.<p>Just a cautionary tale.
Sometimes, the old(er) stuff just werkz.<p>P.S. I'm an old grognard who thinks Node is specifically out to assassinate their sanity. YMMV.