Skip to content

Moving from Vite default to Bun default#924

Merged
jwoertink merged 3 commits intomainfrom
baking_buns
Apr 6, 2026
Merged

Moving from Vite default to Bun default#924
jwoertink merged 3 commits intomainfrom
baking_buns

Conversation

@jwoertink
Copy link
Copy Markdown
Member

Closes #917
Closes #916
Closes #913
Closes #893

Instead of default all new apps to Vite, @wout has put in some serious effort to just making Bun work out of the box. ref luckyframework/lucky#1931

This PR sets up all new browser apps to just use Bun out of the box. This requires no additional dependencies, it's 100x faster at bundling assets, supports typescript, and static assets with cache busting, and no special config is needed to make things "just work".

Now, Webpack and Vite will still be usable (at least for a while), so existing apps won't have to switch over, but this gives new apps a huge benefit in simplicity.

@jwoertink
Copy link
Copy Markdown
Member Author

There is possibly one strange bug I got locally while testing... When setting up a fresh app on my local machine, it all worked perfect, but when booting the app in Docker, I was getting this infinite page reload happening caused by the bun_reload_connect_tag. Maybe I have something wrong in Docker, or it's a legit bug... I'm not sure.

@jwoertink jwoertink merged commit 761742c into main Apr 6, 2026
12 checks passed
@jwoertink jwoertink deleted the baking_buns branch April 6, 2026 23:52
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

Successfully merging this pull request may close these issues.

Compiled javascript ends up in public/ and public/assets/ directories Vite auto-reload (HMR?) Default generated apps to using Vite instead of Mix

2 participants