feat: add preliminary support for Bun

[Strengthless]

Closes #489.

Changelogs:

• Added --use-bun flag, similar to the current --use-yarn flag.
• Added parseBunLockfile.ts to convert bun.lockb into yarn v1 lockfiles.
• Updated getPackageResolution.ts to handle bun conversions before parsing.
• Updated detectPackageManager.ts to detect bun, bun workspaces and multiple lockfiles.
• Updated README with setup instructions for Bun.

Caveats:

• If user has multiple lockfiles, patch-package uses npm by default. However, in the rare case where only bun.lockb and yarn.lock files exist, we have to resort to using yarn. This behaviour has been documented in the CLI and README (see 0491b91).
• Currently awaiting confirmation on how Bun handles postinstalls, for writing up the README about bun setup. (Will bun remove execute postinstall scripts? If not, bun users should also install postinstall-postinstall just like yarn v1 users.)
  • Confirmed by feat: add preliminary support for Bun #490 (comment).
  • Fixed by 7482db9.
• Currently awaiting confirmation on how Bun workspaces work, for writing up the README about bun workspaces setup (Is it similar to yarn workspaces, where users need to "repeat the setup process for the child package" if they want to patch un-hoisted packages?)

Temporary workaround (while this PR is unmerged):

• Citing support patching dependencies, similar to pnpm patch/patch-package oven-sh/bun#2336 (comment),

  Attempting to create a patch using bunx patch-package <package-name> fails.

  However, if you have pre-existing patches in the ./patches directory, you can successfully apply them using the bunx patch-package command (or via package.json -> scripts -> "postinstall": "patch-package")

  As a temporary workaround to generate a patches/package+name+version.patch file

  • run bun install --yarn it just converts bun.lockb into a yarn.lock. (or bun ./bun.lockb > ./yarn.lock)
  • make the necessary modifications inside node-modules/<package-name>
  • bunx patch-package <package-name>
  • rm yarn.lock
  • package.json -> scripts -> "postinstall": "bunx patch-package"
    https://github.com/ds300/patch-package

[OnurGvnc]

I tried bun remove <package-name> and saw that it executes the postinstall script.

❯ bun remove zod
bun remove v1.0.0 (822a00c4)
patch-package 8.0.0
Applying patches...
@remix-run/dev@1.19.3 ✔
@remix-run/react@1.19.3 ✔
 - zod

 1 packages removed [38.00ms]

[Strengthless]

This PR is now ready to merge, with only two caveats as mentioned in #490 (comment).

@ds300 Can you please review this PR? :)

[robertherber]

Looking forward to this :) Been using pnpm for a while and been missing patch-package - so having it work with bun will be yummy!

Hoping this will work in monorepos as well!

[lovlyx]

any news on this?

[rikur]

Wish I could use patch-package to patch patch-package with this patch 😂 I guess I just need to fork the repo.

[robertherber]

Until this is merged, would you consider publishing this fork on npm @Strengthless?

[erickreutz]

LGTM!

[medv]

It's happening!

Using this method for now oven-sh/bun#2336 (comment)

[robertherber]

@ds300 I understand you probably have lots going on - but having this merged would be a key enabler! 🙏🙂

[miblanchard]

Until this is merged, would you consider publishing this fork on npm @Strengthless?

@robertherber I am trying to use this method right now and published it under @miblanchard/patch-package@8.0.12 until this is merged and published.

[RodolfoSilva]

@ds300, could you please review and merge this PR? 🙏

[RodolfoSilva]

Workaround to use patch-package with Bun without needing to keep a yarn.lock file in the project or modify bunfig.toml:

Add this script to package.json:

"patch:create": "bun install --yarn && patch-package $npm_config_pkg; rm -f yarn.lock"

Then generate a patch by running:

bun run patch:create --pkg=[PACKAGE]

This temporarily generates a yarn.lock file, creates the patch, and removes the lock file afterward.

Another alternative, using a package script and bash:

scripts/patch.sh

#!/usr/bin/env bash
set -uo pipefail
bun install --yarn
bunx patch-package "$@"
rm -f yarn.lock

"patch:create": "bash scripts/patch.sh"

Then generate a patch by running:

bun run patch:create [PACKAGE]

And just in case something weird happens, add yarn.lock to .gitignore.