fix(scripts): launch dev tools through current Bun executable#192
Merged
Conversation
DavidBabinec
marked this pull request as ready for review
July 6, 2026 14:30
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
1 participant
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.
What changed
process.execPathfor child Bun invocations.bun run dev, E2E dev, and localstartlaunchers to run CMS/Vite/build commands through that helper.vite/bunchild spawns in these launchers.Why
Windows users with Bun installed via npm can hit
uv_spawnENOENT when a script spawns package-bin shims likevitedirectly, or spawnsbunby name. Routing through the current Bun executable andbun run viteavoids relying on Windows.cmdshim resolution.Impact
bun run devshould no longer fail after the CMS starts withuv_spawn 'vite'on Windows. The same process-launch pattern is also fixed forscripts/e2e-dev.tsandscripts/start.ts.Verification
bun test src/__tests__/devWorkflow.test.tsbun run lintbun run buildbun test