-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(core): add bun package manager #19113
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
6b7fa77
to
d91a1a2
Compare
d91a1a2
to
641cff8
Compare
641cff8
to
d1d1f16
Compare
d1d1f16
to
0f67258
Compare
Oh yay, support for bun as package manager would be VERY much appreciated! |
929edc6
to
247c183
Compare
247c183
to
1f5685d
Compare
I believe this is complete now. Using the same changes as a patch file currently with no issues |
1f5685d
to
8db8c48
Compare
8db8c48
to
0663533
Compare
Bun 1.0.2 fixes the event loop so now appears to be working (unless they break anything else by mistake) |
0663533
to
8c35590
Compare
Bun uses yarn lock for it's binary file. Running the binary will produce the content of a yarn lock file (v1)
8c35590
to
0f8a5dc
Compare
I'm closing this PR. Bun is amazing no doubt it maybe great. The team doing amazing things however its still way too young and running of hype. Bun package manager is playing especially on NX repo. Using node as runtime 1.0.2 hasn't produce dis folder but claiming it ran ok which will be miss leading. If anyone wants to use it, you can use patch package solution here the patch file: https://gist.github.com/Jordan-Hall/e910402a31b4a1e5a0b78324d6595618 its exactly the same as the PR |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Bun uses yarn lock for it's binary file. Running the binary will produce the content of a yarn lock file (v1)
Other option is to use the -y command on add and install. This will create a yarn lock file and then createLockFile can just modify the yarn.lock file instead?