fix(ui): drop --bun flag from Vite dev script#244
Merged
streamer45 merged 2 commits intomainfrom Apr 3, 2026
Merged
Conversation
The dev script used `bunx --bun vite`, which forces Vite to run under Bun's JavaScript runtime instead of Node.js. Vite v8's dep optimization (rolldown) runs 100-1000x slower under Bun's runtime: bunx --bun vite: 27s cold / 242s warm vite (Node.js): 200ms cold / 200ms warm This also caused connection hangs and timeouts because the dev server was stuck in the slow optimization phase and couldn't serve requests. Using bare `vite` (resolved from node_modules/.bin) is idiomatic and consistent with the existing `build` and `preview` scripts. When invoked via `bun run dev` (from `just ui`), Bun still handles script launching and package resolution, but Vite itself executes on Node.js as designed. Signed-off-by: Devin AI <devin@streamkit.dev> Signed-off-by: StreamKit Devin <devin@streamkit.dev> Co-Authored-By: Claudio Costa <cstcld91@gmail.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
devscript inui/package.jsonusedbunx --bun vite, which forces Vite to run under Bun's JavaScript runtime instead of Node.js. Vite v8's dep optimization (rolldown) runs 100–1000x slower under Bun's runtime, causing the slowjust uistartup and connection hangs/timeouts:bunx --bun vitevite(Node.js)The fix removes the
--bunflag so thedevscript uses barevite(resolved fromnode_modules/.bin). This is consistent with howbuildandpreviewscripts already work in the same file. When invoked viabun run dev(fromjust ui), Bun still handles script launching and package resolution, but Vite itself executes on Node.js as designed.Review & Testing Checklist for Human
just uiand verify dev server starts in <1s (vs 27s+ before)http://localhost:3045and confirm the page loads instantly without hangs or retriesNotes
The
--bunflag has been present since the initial commit ofpackage.json. It was likely added to leverage Bun's faster runtime, but Vite v8 has significant compatibility/performance issues when executed under Bun's runtime — particularly in the dep optimization phase which uses rolldown internally.Link to Devin session: https://staging.itsdev.in/sessions/f0d68faf7b7d461981b676f000c47aa1
Requested by: @streamer45