patch-package icon indicating copy to clipboard operation
patch-package copied to clipboard

Fix broken node modules instantly 🏃🏽‍♀️💨

Results 243 patch-package issues
Sort by recently updated
recently updated
newest added

The installation size of the `patch-package` is reaching 2.33 MiB: (https://packagephobia.com/result?p=patch-package) And here is the current npm dependency graph of the `patch-package`: https://npmgraph.js.org/?q=patch-package#zoom=w I am wondering if we can reduce...

``` ./node_modules/.bin/patch-package klinecharts patch-package 8.0.0 • Creating temporary folder • Installing [email protected] with npm ``` it tooks long time , Is there has `--loglevel verbose` to see what hangs?

Hey ds300, I am getting the following issue in CI ``` $ patch-package internal/modules/cjs/loader.js:985 throw err; ^ Error: Cannot find module './dist/index.js' Require stack: - /home/node_modules/.bin/patch-package at Function.Module._resolveFilename (internal/modules/cjs/loader.js:982:15) at...

First of all, thanks again for all of the hard work and maintenance that goes into `patch-package`. It's also an inspiration for other tools in the ecosystem, leading to the...

![image](https://github.com/ds300/patch-package/assets/26792399/40f4b583-80cc-4b43-93e4-4151a65de72e)

Hello This is kind of a feature request. This library directly depends on json-stable-stringify, which depends on jsonify, which has no license and thus cause problems with corporations, at least...

I changed something in the package @sentry. Then tried running `npx patch-package @sentry` to add to my permanent fixes. That throws this error: > No such package @sentry File not...

Trying this with a package, and it says there are no changes, however there are. The changes are in the package.json of this package, not sure if that is why...

As mentioned in https://github.com/oven-sh/bun/issues/2336#issuecomment-1712458657, > Attempting to create a patch using bunx patch-package fails. The patch-package outputs the following error: > ``` > **ERROR** No package-lock.json, npm-shrinkwrap.json, or yarn.lock file....

As in the title, it seems that the latest version (8.0.0) fails on a package during `postinstall` but not when re-running `patch-package`. I did some investigations and it seems that...