chore: split vitest and vite configs#4568
Merged
wescopeland merged 2 commits intoRetroAchievements:masterfrom Feb 19, 2026
Merged
chore: split vitest and vite configs#4568wescopeland merged 2 commits intoRetroAchievements:masterfrom
wescopeland merged 2 commits intoRetroAchievements:masterfrom
Conversation
Jamiras
approved these changes
Feb 19, 2026
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
2 participants
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.
When running
pnpm dev, Vite starts a dev server with hot reload enabled on a specific port. If you then runpnpm testin another terminal tab, it reads the same vite.config.ts file and spins up its own internal Vite server.Because they share the same config, Vitest's Vite instance conflicts with the already-running dev server, and it blows your local dev server's internal assets away. I have to always restart
pnpm devafter running tests.This is fixed in this PR by splitting out Vitest's config into its own file. There are no functional changes as part of this PR, it's purely a QoL local dev improvement. I'm probably the only one who gets hit by this regularly - I only just now realized it's because of the single config file.