luckyframework
Thoughts on shipping with Bun by default?
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 https://github.com/luckyframework/lucky/blob/5607fe69ce631569bed96376cc5f36654f95fcce/tasks/watch.cr#L127
Related: https://github.com/luckyframework/lucky_cli/issues/346
I also use Bun in my app. It's mature and future proof IMO. No reason to use something else. Also, are there lucky prod apps in the wild using the front-end vanilla setup ? It's not that a critical choice. Unlike other lucky opiniated choices (postgresql, lucky HTML) this one can be tossed out easily.
