Skip to content
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

Thoughts on shipping with Bun by default? #1931

Open
jwoertink opened this issue Nov 11, 2024 · 0 comments
Open

Thoughts on shipping with Bun by default? #1931

jwoertink opened this issue Nov 11, 2024 · 0 comments

Comments

@jwoertink
Copy link
Member

Bun is pretty neat and SUPER fast compared to Yarn. When Lucky first released in 2017, using Yarn was common. Now several years later, there's a lot of choices out there.

The tough part about setting a default is that not everyone will want to use that. Also not everyone will be able to use that. My main app doesn't run with npm or Yarn 2.0+... things just tank. I have to use the 1.0 branch of Yarn to do anything... With that said, there's already ways to use other setups with Lucky just by changing up a few things in your code, so escaping out to any other system is already supported, but with how the javascript world works, we have to have something as a default. Why not have it be something super fast?

I want to avoid the "let's just give a choice" option because that adds a huge level of complexity and maintainability, and with it being mainly just me at the moment, I don't want to add a ton of extra work.

Also, this would be mainly a change to LuckyCLI, but we would need to update the browser-sync option here

"yarn run browser-sync reload --port #{Lucky::ServerSettings.reload_port}",

Related: luckyframework/lucky_cli#346

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant