vue-cli VS devtools

Immerse yourself in the official Vue CLI documentation for a deeper understanding.

Security would be a useful benefit/section to add to this post:

A.) If maintainers of your dependencies edited an existing version.

B.) If your dependencies did not pin their dependencies.

For instance, if you installed vue-cli in May of last year from NPM with --prefer-offline (basically the same as checking in your node_modules), you were fine. But because vue-cli doesn't pin its dependencies ("node-ipc"), installing fresh/online would create WITH-LOVE-FROM-AMERICA.txt on your desktop [1], which was at the very least a scare, but for some, very problematic.

[1] https://github.com/vuejs/vue-cli/issues/7054

Vue CLI documentation: https://cli.vuejs.org/

An interesting fact is that this dependency was used in vue-cli.

Vue CLI 3

Open issue for half a year https://github.com/vuejs/vue-cli/issues/7234

Vue CLI (command-line interface), which is used to install and create the main Vue framework libraries and third-party plugins.

Is there a reason you've used the old Vue CLI though, with webpack and babel?Imho you're missing a lot not using Vite... npm init vue@latest (create-vue) is the recommended way to scaffold a new Vue app, Vue CLI is in Maintenance Mode

The official Vue CLI UI is made with Vue + Apollo GraphQL. You'll know it when you run vue ui in your terminal. - https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue/cli-ui

Both Vue.js and React have their own set of tools and libraries to help developers build and maintain their applications. Vue.js has Vue CLI and Nuxt.js, while React has Create React App and Next.js.

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