patch-package
patch-package copied to clipboard
Fix broken node modules instantly 🏃🏽♀️💨
I'm using yarn to manage some native iOS dependencies by simply adding them: ```sh yarn add https://github.com/SnapKit/SnapKit#4.2.0 ``` But when I try to patch the package:  It would be...
# 🐛 bug report On a lerna-based monorepo, there are some issues with patch-package. Suppose I have this folder structure... ``` . ├── ... ├── packages │ ├── a │...
``` diff --git a/node_modules/@react-native-community/masked-view/android/src/main/java/org/reactnative/maskedview/RNCMaskedView.java b/node_modules/@react-native-community/masked-view/android/src/main/java/org/reactnative/maskedview/RNCMaskedView.java index 289d287..bac74c1 100644 --- a/node_modules/@react-native-community/masked-view/android/src/main/java/org/reactnative/maskedview/RNCMaskedView.java +++ b/node_modules/@react-native-community/masked-view/android/src/main/java/org/reactnative/maskedview/RNCMaskedView.java @@ -35,7 +35,9 @@ public class RNCMaskedView extends ReactViewGroup { // draw the mask if (mBitmapMask != null)...
This happened because the patch file patches\react-native+0.61.5-jitsi.2.patch could not be pa rsed. If you just upgraded patch-package, you can try running: cd patches\react-native+0.61.5-jitsi.2.patc patch -p1 -i h npx patch-package react-native...
Updates package.json to: * Include `src` which enables setting breakpoints in patch-package code when it's not running, and enables you to navigate from breakpoints in VSCode to the corresponding source...
I was trying to use patch-package and there was a failure which is probably caused by accidentally using patch-package to try to patch a local fork of a package. But...
Hi there, this is a re-opening of #147. I have just experienced the same issue as the original poster. I made a patch on macOS that successfully applied on multiple...
Per https://github.com/ds300/patch-package/issues/84, it is not safe to publish npm packages with patched dependencies. This notice should be prominent in patch-package documentation. Note: I don't expect this PR to be merged...