Repository navigation
Conversation
RSS1102
force-pushed
the
feat/vitest-cli-completion
branch
from
October 24, 2026 21:17
67aab9c to
fb794e5
Compare
This branch has not been deployed
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.
Related to #2953.
Generate completion metadata at build time by read-only traversal of the public CAC fields returned by
vitest/node.createCLI(), following the Vitest discussion. The global Rust CLI reads the packaged metadata to completevp testcommands and option names without starting Node.js, loading project configuration, or triggering installation.Completion follows the selected local Vite+ package and falls back to the existing behavior when metadata is missing, unsupported, or mismatched. Option values and test execution compatibility are outside this first draft.