feat: integrate vite devtools#226
Draft
arashsheyda wants to merge 6 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
🔗 Linked issue
closes #9
❓ Type of change
📚 Description
this PR adds
comark/devtoolsto vite devtools and fixes the React component to work in client-side environmentsVite DevTools Integration
@comark/vue/viteso user only need to register the Vite DevtoolsOther changes
while working on the devtools I found a bug with react example while vite devtools enabled:
which the fix resulted in
<Comark>component being no longer async, works in both client and server contextsScreen.Recording.2026-05-31.at.1.00.26.AM.mov
📝 Checklist
pnpm verifyand it passes.