New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devtools Kit #71
Comments
Maybe a first step would be to publish a package containing some TS types that describe all the expected APIs? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
✏️ This is a draft note about a unified set of standard APIs to create devtools. I discussed about this a bit with @antfu too and trying to write down some ideas about it.
The idea is to standardize things to be able to :
One one side create shells to host dev tools
On the other side create devtools applets/plugins to implement various tooling and development features
Use cases
Then creating the equivalent of the current Nuxt devtools would be to pick a "embedded pane" shell and add various applets like "pages", "routing", "auto-imports"... For Vue devtools, it would be different set of applets.
Then we could put all of those applets into a "standalone app" shell and it would still work because communication between "Devtools UI" and "In the page" contexts are abstracted away.
A multi-devtools app like guijs could also implement this standard and have working vue components tree directly inside it. New applets ideas coming from it could be installing packages, killing ports, etc.
The text was updated successfully, but these errors were encountered: