This repository was archived by the owner on Jan 6, 2024. It is now read-only.
chore: migrate to vite-plugin-devtools#107
Open
Aslemammad wants to merge 9 commits intowebfansplz:mainfrom
Open
chore: migrate to vite-plugin-devtools#107Aslemammad wants to merge 9 commits intowebfansplz:mainfrom
Aslemammad wants to merge 9 commits intowebfansplz:mainfrom
Conversation
Author
|
for it to be working, you need to clone vite-plugin-devtools first, and link it using pnpm first you need to build vite-plugin-devtools first ( I think you can have a review so I see what can be changed, I believe there's more space to do more clean ups though. Thank you so much for the opportunity @webfansplz. We appreciate you. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR tries to bring vite-plugin-devtools as the base core for vite-plugin-vue-devtools.
This will help this devtools to be aligned with other devtools (like nuxt-devtools) and let them work next to each other easily. It also helps avoiding rewriting many of the core APIs, so other devtools can also benefit from those APIs (Server-Client communication, panel UI, ...).
At some point we'd have such experience:
