vuesion VS devtools

I use them in all of my input components: https://github.com/vuesion/vuesion/tree/next/src/components/input-and-actions

I can provide you with my knowledge about Vue 2/nuxt2: https://github.com/vuesion/vuesion and Vue 3/nuxt3: https://github.com/vuesion/vuesion5

https://github.com/vuesion/vuesion or for nuxt3/vue3: https://github.com/vuesion/vuesion5

I have a repo with Vue2 (Nuxt.js 2) + composition api and storybook: https://github.com/vuesion/vuesion

https://github.com/vuesion/vuesion has GQL setup included

one exception is using plugins like i18n, they can also be used inside presentational components because they are pretty easy to integrate (no specific set of configuration per use-case) into storybook and tests. if you want to see my setup, go to https://github.com/vuesion/vuesion

I have a nuxt2 boilerplate that uses composition api already. Should hopefully be easy to migrate to nuxt3 later this year: https://github.com/vuesion/vuesion. I hope it helps you to make a decision

We maintain a (nuxt) template project that new projects are forked from. It contains all the settings and libraries that we minimally need for an app. I think it's important to have your own template project, rather than use someone else's.

Give this a shot: https://github.com/vuesion/vuesion

I maintain a reference project as boilerplate here: https://github.com/vuesion/vuesion. let me know if you have any questions.

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