The project only introduces vue.js files, so does it make sense to use vue in the project?

when I use vue-cli scaffolding to do a project these days, I feel like there are a lot of holes to step on. I wonder if the project only introduces the vue.js file, similar to the introduction of JQ to use vue to do so, will it take advantage of vue

Mar.20,2022

the purpose of scaffolding is to save developers time to deploy the project and make some common configurations in advance.

if it is just to do some data processing with vue, of course, the official document is also introduced directly at the beginning


the best way is scaffolding. It is also possible to introduce
directly.

VUE is a progressive framework

as long as it suits you, no one cares about the difference between your suit with sneakers and your suit with leather shoes.


certainly makes sense, you can use vue.js directly to build traditional multi-page applications just like introducing jQuery. But you have to consider whether your project needs to be compatible with browsers that don't support es6, and use babel if you need to. Vue-cli exists for the engineering of medium and large projects, regardless of personal choice.


I think the advantage of mvvm is to ensure the consistency of data and dom, while spa solves the performance problems of the traditional development mode. The whole bucket and plug-ins such as routing and data flow
if you consider the subsequent functions are better compatible with scaffolding, if the page is just a form submission, it is up to you


not. Might as well quote jq. directly Scaffolding is to lighten the burden of development. Direct quotation may encounter more holes, and no one has encountered it, and you can't find it on the Internet.


is all right.
new Vue () an instance on each page, but it is cumbersome and the components cannot be reused.


I think it depends on the size of the project. If it is a small project, it is more convenient to introduce vue.js directly. If it is medium or large, it is a bit simple and rough from the whole family bucket.


when you want only one or more parts of the page to be controlled by vue, it is clear that introduction provides better freedom.

separating vue instances can also achieve better data isolation.

give an inappropriate example:

for example, for a so-called medium-and large-scale project, now we need to do the function of a propaganda page, which requires the page to go straight out as soon as possible, so simple that it only takes a few asynchronous requests to complete the data interaction. You add it to the whole scaffolding project. I visit this page alone and load a bunch of routes? What if I directly take the page as a static page and render it with a small vue instance according to the access parameters?

so it's not that a project can only be introduced in one way, depending on the situation.

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1b3c57e-2c2fc.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1b3c57e-2c2fc.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?