fix(build): resolve workspace test runner consistently - #184
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
badcuban
force-pushed
the
fix/vite-plus-workspace-test-runner
branch
from
August 24, 2026 19:08
e72c1f4 to
3a48c0a
Compare
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.
On Windows, workspace test scripts could resolve the global Vite+ binary instead of the repository-pinned binary and fail during test collection with
Cannot read properties of undefined (reading config).Route every workspace test entry point, including the browser-test task, through
vp exec vp. This follows the command pattern already used by CI, stays cross-platform, and does not require a lockfile change.Verification:
vp test runcollection failure on Windows