vue-cli VS Vue.js

Recently, a ticket was added to our sprint with the goal of reducing packages with critical and high vulnerabilities in a legacy project. The task involved migrating a Vue 2 project using Vue CLI as the build tool to Vite.

Ecosystem: Vue's ecosystem is smaller than React's but rapidly growing. The Vue CLI provides a robust tool for project scaffolding and build configuration.

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

But it does not deal with all the non-JSON objects, e.g. Map or other class instances that are not even JSON-serializable by default.

Best to use TypeScript, and ideally, it should only be needed to do such checks when dealing with foreign data.

When data comes from parsing JSON, the check above should be enough.

When authoring complicated library code that needs reflection, I think it's worth looking at Vue2's hilarous solution:

  https://github.com/vuejs/vue/blob/547a64e9b93d24ca5927f653710b5734fa909673/src/util/lang.js#L293

Recently, a ticket was added to our sprint with the goal of reducing packages with critical and high vulnerabilities in a legacy project. The task involved migrating a Vue 2 project using Vue CLI as the build tool to Vite.

Vue.js is a tool for building user interfaces. It's easy to use and works well for both small and big projects. I specifically love the team behind Vue and Nuxt! Highly recommend checking it out and giving it a try. It has 208k stars 🌟. Explore Vue.js here.

Repository: Vue.js

GitHub Repository - The main Vue.js repository.

Vuejs

Vue.js is a big favorite for making websites because it's easy to use and fits in well with other stuff. Many people worldwide are using it, and the community keeps growing.

Vue has a thriving ecosystem with a wide range of third-party libraries and plugins available for extending its functionality. These libraries cover everything from state management to routing, making it easy for developers to find solutions to common problems and enhance their development workflow. As of this writing, Vue has 200k GitHub stars.

6. Vue.js