devtools VS vue-next

I've tried everything listed here for v3/standalone devtools and had no luck. Either CSP issues related to V3 or the inspector complains about the source maps not being found, but clicking the link brings you to the file location.

Vue Devtools

It seems as though it may be this issue: https://github.com/vuejs/devtools/issues/1974

The VueJS DevTools has a different team with a different leader. That's collaboration.

I think you are missing an important part here, this extension is open source, meaning everyone can check what they do with the info, meaning if something fishing is happening would be a big mess. for me, there is nothing to be worry about. you can also read the code and check. https://github.com/vuejs/devtools

All I can suggest is Vue Devtools

I don't know for sure, but I think the vue-devtools browser plugin ( https://github.com/vuejs/devtools ) works with the dev server to help track and debug state (mutations, actions, etc) as well as template issues, etc. I'm not sure how it works. I assume it's 10% code and 90% magic of some shade.

Source: Devtools

⚡️ Vue 3 & Vite

The project at the moment has completed feature parity with @vue/compiler-core . Compiling to dom, ssr, sfc have not yet been implemented. You can check what has been implemented in the playground

For this to work, you will need to be using vue@^3.2.25 and above. No additional dependencies are required. Vue 3.2.25+ ships an implementation under the package @vue/reactivity-transform. It is also integrated (with its APIs re-exported) in @vue/compiler-sfc so most userland projects won't need to explicitly install it.