Conversation
…ojects API `bun test` invokes Bun's built-in test runner, not the `"test": "vitest"` script — completely bypassing vitest config (environment, plugins, etc.). `vitest.workspace.ts` was silently ignored since vitest 4 removed the workspace file in favor of `test.projects` in the root config. Tests were falling back to the root config with no `environment: "happy-dom"`.
Move sponsors below highlights so the value proposition comes first. Remove duplicate AI assistant mention from description (already in badges and "Need Help?" section).
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.
Problem
Two issues causing CI tests to silently run in the wrong environment:
bun test≠bun run test—bun testinvokes Bun's built-in test runner, not the"test": "vitest"script frompackage.json. Bun's runner ignores all vitest config (environment, plugins, etc.).vitest.workspace.tssilently ignored — The workspace file was removed in Vitest 4 in favor oftest.projectsin the root config. With the file ignored, vitest fell back to the root config which had noenvironment: "happy-dom", so DOM-dependent tests would fail.Changes
ci.ymlbun test→bun run test -- --run--rundisables watch modevitest.config.tstest.projects: ["apps/*"]vite.config.tsprovides its ownenvironment, plugins, etc.vitest.workspace.tsBefore / After