-
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
Executors for Bun #19093
Comments
They still alot to do on bun yet before it could be considered main repo. Just like the deno work in nx-lab. If you want to help and start using bun now checkout https://github.com/Jordan-Hall/nx-bun/ I also think this should stay in decisions personally. Check out the team response #11048. It's also worth Noting hype doesn't equal popularity. It's the new "in thing" but most of use remember when deno was realised. Hype and test it out but back in the real world we all use node. bun is also not 100% compatible with all of npm and node too. Lack of windows full support is a major issue. I created an will keep updating bun until time it nx wants it (if ever) because I actually like one of the backend framework. |
Yeah, lets keep bun discussion in the discussions, its been a pretty active one and I don't see benefit to moving it here. Our stance has currently not changed, but its something we are watching. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Description
Implement executors for the following Bun CLI commands
My suggestion for the package name would be
@nx/bun
Motivation
Bun recently released version 1.0.0 and it has been gaining in popularity.
The text was updated successfully, but these errors were encountered: