Repository navigation
fix: register Vite DevTools for devframe discovery - #579
Merged
Merged
Conversation
antfu
approved these changes
Sep 17, 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.
Description
devframe connectcan't discover Vite DevTools because its hub isn't registered. This registers it whenever a Vite server is present, with the Vite DevTools name and the inspected project's directory. It also covers Nuxt's Vite middleware server.Registration still starts after the first request gives the hub its origin.
Linked Issues
None.
Additional context
There could also be an option to opt out of registration if we find a use case for it. For now, automatic discovery seems like a sensible default.