Update bundle mode patch guide to add bun patching instructions

[acarlson33]

Added instructions for using bun without patch-package for better compatibility with bun.

Summary

There weren't any instructions for patching bun repositories, and patch-package by itself doesn't work because in monorepos at least, bun installs deps into the .bun folder inside of node_modules, which breaks patch-package. I added a section to the patching instructions that details how to use bun's built in patching mechanisms along with git to make the patches for bun monorepos with isolated linking.

Test plan

This is just a documentation change, but I've verified the patches are successful, and you can do so by following the instructions added into the file.

[jsg2021]

You don't need patch-package with bun.

Just apply them with git and commit.

# download patches
curl -fsSLO https://github.com/software-mansion/react-native-reanimated/raw/refs/heads/main/packages/react-native-worklets/bundleMode/patches/patch-package/metro-runtime/metro-runtime+0.84.4.patch
curl -fsSLO https://github.com/software-mansion/react-native-reanimated/raw/refs/heads/main/packages/react-native-worklets/bundleMode/patches/patch-package/metro/metro+0.84.4.patch

# apply
bun patch metro-runtime #optional... if you know the package is clean, you can skip
(cd node_modules/metro-runtime apply ../../metro-runtime+0.84.4.patch)
bun patch --commit metro-runtime

bun patch metro
(cd node_modules/metro && git apply ../../metro+0.84.4.patch)
bun patch --commit metro

# cleanup
git add patches package.json
git commit -m "chore: patch metro"

rm ,/metro*.patch

[acarlson33]

You don't need patch-package with bun.

Just apply them with git and commit.

# download patches
curl -fsSLO https://github.com/software-mansion/react-native-reanimated/raw/refs/heads/main/packages/react-native-worklets/bundleMode/patches/patch-package/metro-runtime/metro-runtime+0.84.4.patch
curl -fsSLO https://github.com/software-mansion/react-native-reanimated/raw/refs/heads/main/packages/react-native-worklets/bundleMode/patches/patch-package/metro/metro+0.84.4.patch

# apply
bun patch metro-runtime #optional... if you know the package is clean, you can skip
(cd node_modules/metro-runtime apply ../../metro-runtime+0.84.4.patch)
bun patch --commit metro-runtime

bun patch metro
(cd node_modules/metro && git apply ../../metro+0.84.4.patch)
bun patch --commit metro

# cleanup
git add patches package.json
git commit -m "chore: patch metro"

rm ,/metro*.patch

Thanks for that, I doubt I would have figured out there would be a way to do it with git as I don't patch packages super often. I refactored the doc to include that instead of using patch-package. I didn't add the rm command yet, (I will in a future commit here soon), but I think it'll have to look like this: rm ./patches/metro+*.patch && rm ./patches/metro-runtime+*.patch I figure that's a safer option because running bun patch --commit 'node_modules/metro' will cause bun to create a patch of the package that you can commit to the repo but it does so with a naming convention like this: metro@0.84.4.patch. We don't want to remove these patch files so installing the deps on another machine or clearing node_modules and reinstalling doesn't cause bun to error when it tries to apply the patch on installation. However, we should be able to remove the patch-package ones we initially used.

[jsg2021]

You don't need patch-package with bun.

Just apply them with git and commit.

download patches

curl -fsSLO https://github.com/software-mansion/react-native-reanimated/raw/refs/heads/main/packages/react-native-worklets/bundleMode/patches/patch-package/metro-runtime/metro-runtime+0.84.4.patch

curl -fsSLO https://github.com/software-mansion/react-native-reanimated/raw/refs/heads/main/packages/react-native-worklets/bundleMode/patches/patch-package/metro/metro+0.84.4.patch

apply

bun patch metro-runtime #optional... if you know the package is clean, you can skip

(cd node_modules/metro-runtime apply ../../metro-runtime+0.84.4.patch)

bun patch --commit metro-runtime

bun patch metro

(cd node_modules/metro && git apply ../../metro+0.84.4.patch)

bun patch --commit metro

cleanup

git add patches package.json

git commit -m "chore: patch metro"

rm ,/metro*.patch

Thanks for that, I doubt I would have figured out there would be a way to do it with git as I don't patch packages super often. I refactored the doc to include that instead of using patch-package. I didn't add the rm command yet, (I will in a future commit here soon), but I think it'll have to look like this: rm ./patches/metro+*.patch && rm ./patches/metro-runtime+*.patch I figure that's a safer option because running bun patch --commit 'node_modules/metro' will cause bun to create a patch of the package that you can commit to the repo but it does so with a naming convention like this: metro@0.84.4.patch. We don't want to remove these patch files so installing the deps on another machine or clearing node_modules and reinstalling doesn't cause bun to error when it tries to apply the patch on installation. However, we should be able to remove the patch-package ones we initially used.

the rm command just removes the downloaded source patches. you don't want to delete the files in the patches directory that bun creates.

[acarlson33]

The command I made filtered the patches by whether or not the patch files have the + in them. The bun ones will be filtered out because they contain @, so it shouldn't be an issue.

[jsg2021]

@acarlson33 yes, you are correct. My example put the source patches in a different directory to avoid the collision, and so it didn't need to handle the filter.

I probably should have output to /tmp or something to make that clearer. But anyways. I like to keep things as simple as possible. The more flags & filters we add to readmes, the more intimidating it is for the less experienced.