feat: add Bun to init command

[TMisiukiewicz]

Summary:

Adding support for Bun package manager with init command.
With template and dependencies installed via bun package manager, the JS code execution time went from ~41s to ~2,5s.

In order to make package managers easier to use, this PR deprecates --npm flag and introduces --pm flag where it's possible to use one of the packagers: yarn, npm or bun.

Test Plan:

Follow the contributing guide

1. Run init command as usual. It should install template and dependencies using yarn and you should have yarn.lock file in created project.
2. Run init command with --pm yarn flag. Once it's done, you should have yarn.lock file in created project.
3. Run init command with --pm npm flag. Once it's done, you should have package-lock.json file in created project.
4. Run init command with --pm bun flag. Once it's done, you should have bun.lockb file in created project.
5. Run init command with --npm flag. It should show a deprecation warning in the console.
6. Run bun run ./path-to-cli init ProjectName. It should use bun to install dependencies and template without any additional flag passed. Should also work with bunx once deployed.
7. If bun is not installed on the machine, it should fallback to npm. Created project should have a package-lock.json file. throw an error that selected package manager is not available (only when using flag)
8. Run clean command in the created project - the Bun option should be available. It runs bun pm cache rm under the hood.

Checklist

• Documentation is up to date to reflect these changes.
• Follows commit message convention described in CONTRIBUTING.md

[jaworek]

If bun is not installed on the machine, it should fallback to npm. Created project should have a package-lock.json file.

I think it would be safer to give user an error and let them know that bun is missing or cannot be found in path. Doing fallback to different tool might be unexpected and not something that user wants to do. As an alternative you could ask a followup question whether they want to use npm instead.

[TMisiukiewicz]

If bun is not installed on the machine, it should fallback to npm. Created project should have a package-lock.json file.

I think it would be safer to give user an error and let them know that bun is missing or cannot be found in path. Doing fallback to different tool might be unexpected and not something that user wants to do. As an alternative you could ask a followup question whether they want to use npm instead.

thanks, added this kind of a check 🙌

[shamilovtim]

Will bun be used as the runtime to run metro, prettier, tsc, eslint and so on with this change?

[mani-elumalai]

Nice work

[Jarred-Sumner]

Exciting. Let me know if you run into any issues with Bun

[tido64]

Did you try building the project after initializing a project with Bun? bun react-native run-android --no-packager fails for me with

error Android project not found. Are you sure this is a React Native project? If your Android files are located in a non-standard location (e.g. not inside 'android' folder), consider setting `project.android.sourceDir` option to point to a new location.

[Jarred-Sumner]

If postinstall of react-native dependencies is necessary, that will need to be worked around until we ship the default allowlist for trustedDependencies

[tido64]

If postinstall of react-native dependencies is necessary, that will need to be worked around until we ship the default allowlist for trustedDependencies

Never mind, my workaround for oven-sh/bun#5063 didn't work properly. It works once I've fixed it.

[TMisiukiewicz]

Did you try building the project after initializing a project with Bun? bun react-native run-android --no-packager fails for me with

error Android project not found. Are you sure this is a React Native project? If your Android files are located in a non-standard location (e.g. not inside 'android' folder), consider setting `project.android.sourceDir` option to point to a new location.

Seems to be working

Screen.Recording.2023-09-13.at.12.06.17.mov

[szymonrybczak]

Let's ship it