Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add fyi for using patch-package on EAS (#156)
- Loading branch information
1 parent
b8a1795
commit 3740343
Showing
1 changed file
with
9 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
# Using `patch-package` on EAS | ||
|
||
If you want to make changes to code inside a dependency, [`patch-package`](https://github.com/ds300/patch-package) provides a convenient solution to do that. It allows you to make changes directly to your **node_modules** directory, then generate a patch file that you can commit to source control and will be automatically re-applied to the package in **node_modules** when you run `npm install` (or `yarn`, etc.). | ||
|
||
Out of the box, `patch-package` is fully compatible with EAS. If you follow the [installation instructions](https://github.com/ds300/patch-package?tab=readme-ov-file#set-up) for `patch-package`, including adding the `postinstall` script to your **package.json**, then any patches you have created in your project using `patch-package` will automatically be applied on EAS as part of the 'Install dependencies' step, just like on your local machine. | ||
|
||
> **Note**: make sure that the **patches** folder that is created by `patch-package` is added to source control, so it will be included when your source code is uploaded to EAS. | ||
The output from `patch-package` is available in the logs for the 'Install dependencies' step on your build details page. |