Project Roadmap

[webfansplz]

• Fully compatible with V6 plugin API
• Refactor Messaging Channel
• Ship Browser Extension
• Timeline Panel
• Documentation
  • DevTools packages diagrams
  • Contribution guide
  • Migration Guide
• Integration features into Nuxt DevTools
  • Pinia panel
  • Components panel
• Applet package
  • Reuse core modules/utils with Nuxt DevTools
• Reactivity Tracing feature

[alexzhang1030]

Please be aware that the new vite-plugin-vue-devtools have rewritten all the code, and the functionality will differ compared to the old vite-plugin-vue-devtools. We will migrate gradually.

[Mister-Hope]

I am a bit confused about the project roadmap now, The project is not actively maintained in the past 45 days. But I see there are still plenty of TODOs at this page.

No browser extension releases, but https://www.npmjs.com/package/@vue/devtools-api is using v7 as latest (which I offten upgrades to by mistake.)

So my biggest concern is about the conflict between:

• latest tag with v7, not actively maintained
• Missing roadmaps and no devtool extension (not pretty available for users)

A explanation is appreciated, or at least we may set latest tag back to v6?

Under my understanding, if authors like me want to develop a plugin for the devtool, I shall still publish it with v6. Users are definitely not expected to see a guideline telling them to install the new v7 globally and launch it every time manualy for debugging.

[webfansplz]

I am a bit confused about the project roadmap now, The project is not actively maintained in the past 45 days. But I see there are still plenty of TODOs at this page.

No browser extension releases, but https://www.npmjs.com/package/@vue/devtools-api is using v7 as latest (which I offten upgrades to by mistake.)

So my biggest concern is about the conflict between:

• latest tag with v7, not actively maintained
• Missing roadmaps and no devtool extension (not pretty available for users)

A explanation is appreciated, or at least we may set latest tag back to v6?

Under my understanding, if authors like me want to develop a plugin for the devtool, I shall still publish it with v6. Users are definitely not expected to see a guideline telling them to install the new v7 globally and launch it every time manualy for debugging.

First, I'd like to clarify the maintenance status of the project. We are still actively maintaining it, but we don't have full-time maintainers, we have other work to do, and I appreciate the time and effort that contributors put into it.

Regarding browser extensions, we need to deal with compatibility issues with older versions of the original. Because older versions support Vue2, and there are a lot of users out there. We need to have a good plan to deal with them, and that will take some time.

Regarding the Vue DevTools Plugin API, we are trying to be fully backward compatible with the V6 API to facilitate compatibility with V6 plugins in the ecosystem.

Finally, thanks for your feedback, I have rolled back the latest tag of @vue/devtools-api to v6, hope it will help you.

[gangsthub]

Hi, @webfansplz. First of all, thanks a lot for the effort you and other contributors put into the new devtools! I just tried them inside a Storybook project and they work magnificently. I wanted to ask if there are plans to add Vue component events in the UI too. I'd love to help as well!

[alexzhang1030]

Absolutely! PRs are very welcome!

[gangsthub]

Another question, do you plan to add something like @nuxt/devtools-kit so users can build and register their own tabs?

As seen in: https://devtools.nuxt.com/module/guide

[alexzhang1030]

Yeah, we have a simple plugin-api now, we will consider making this API more powerful.

[webfansplz]

Another question, do you plan to add something like @nuxt/devtools-kit so users can build and register their own tabs?

As seen in: https://devtools.nuxt.com/module/guide

Hi, we made the v6 plugin API backward compatible in v7.3.0, and now users can customize tabs through it. (see: https://devtools-next.vuejs.org/plugins/api)

[kazupon]

Hello!
Thank you for your amazing project!
I have a question.

Recently addCustomTab has been supported. Its API supports iframe, so 3rd tools gives us more freedom for debug tools.
https://devtools-next.vuejs.org/plugins/api#addcustomtab

Currently, I seems that it does not support RPC, are there any plans to do so in the future?

I know from reading the source code that vite-plugin-insect is integrated using addCustomTab.
vite-plugin-insect uses vite's RPC and negociates with its vite dev server and browser client.

I hope that support the RPC between the iframe side and on the vue devtools side.

[webfansplz]

I think supporting RPC messaging for addCustomTab API makes sense. Let's track it in #537

[zhangenming]

what is Reactivity Tracing feature
Visual the vue Reactivity dependency(ref/computed/watch...) graph ?

[alexzhang1030]

We have been thinking about this feature for a long time. The hard point is correctly analyzing the reactivity dependencies (especially for cross files/modules). The runtime analyzer will be great, but it cannot analyze the location in the file of the variable.

We may implement this in the future by combining runtime and compile-time. If you are interested in this, we can have a more in-depth discussion :)

[matthiasPOE]

@alexzhang1030 Im looking for this: vuejs/devtools-v6#862 is this already in here or does it relate to the tracing?

[s3xysteak]

Reactivity Tracing is my favorite feature (in vue2? I have memories of using it), which is really useful. Hope it could come back soon!