Vue CLI 3.0 is released

Yu Creek believes that older versions of Vue CLI essentially just pull templates from GitHub, and there are several problems with this way of pulling templates:

  1. Supporting too many options in a single template can make the template itself extremely complex and difficult to maintain, while providing multiple templates can confuse beginners and make it difficult to share functionality or migrate between templates. CLI 3’s solution to this problem is to support multiple functions in the form of plug-ins, one for each function (such as unit testing). This eliminates multiple templates and improves the MAINTAINability of the CLI itself. At the same time, support third-party plug-ins, so that users can achieve a variety of self-defined function extension.

  2. Pull template generated projects, all webPack configuration and build scripts are directly contained in the repository, once users make changes to these parts, it is very difficult to get updates and upgrades to the source template. CLI 3 generated projects, core Webpack configuration and build logic are encapsulated in dependencies, while allowing users to make low-level changes through configuration files. The advantage of this is that after CLI updates, users can still upgrade even after custom modifications.

  3. Since the core configuration is encapsulated, we have more room to do more complex features and optimizations, such as build-time performance optimizations (caching/multicore), Modern Mode, generating Web Components, etc., without having to worry about users’ projects being riddled with build code unrelated to the application itself. At the same time, with the implementation of new web platform specifications, we can also continue to add various targeted optimization in THE CLI, users only need to upgrade to obtain.

The GUI has long been considered easy to use and efficient with the CLI. The GUI was added to Vue CLI 3.0, Yu Explained, mainly to lower the barriers to entry. Since the command line can show only a limited amount of interaction, the default user has a basic understanding of the various tools and configuration items involved in creating a project. The GUI provides more information to help the user understand what these things do. In addition, the GUI can provide information that is difficult to display on the command line, such as analyzing the size ratio of packaged modules through visual diagrams.

Some UI libraries/VUe-packaged frameworks also provide scaffolding, and Yu Creek believes that most libraries don’t require special configuration. Libraries that provide scaffolding usually require special configuration to enhance the development experience. CLI 3 is intended to provide a standard solution for this situation, so it provides a powerful plug-in API. Ideally, all third-party UI libraries can be plugged into CLI 3 as plugins, such as Vuetify. As for frames (such as the NUXT), it makes sense to have their own scaffolding, since something higher up is involved.

Some time ago, Vue was looking for a full-time open source worker. I’m sure you’re wondering if Vue is a for-profit organization and how they get the money to keep running.

Yu replied that Vue is currently maintained by an independent team and is not a startup funded by sponsors, advertising, etc. Most of the sub-projects are now handled by team members, and the Vue core library is still maintained by You.

To understand Vue team members can stamp the following link: https://vuejs.org/v2/guide/team.html

As for the single point of issue, Yu Said that the single point of issue certainly exists at present. Part of his next plan is to refine the governance Model of the project and reduce the project’s personal dependence on him, but this will take time to implement slowly. Looking beyond the front end, Vue is a very young project, and at this stage it is normal, if not necessary, to rely on core developers. Many of the projects that matter today, like Linux, are also, to some extent, a single point of problem. It’s also hard to predict what Python will do after Guido announces his retirement.

Front always popular with such a word “don’t update, I learn not move”, before someone spoof P figure, says Mr Rain creek to publish the Vue 4.0, especially the rain creek, technical professional itself is a need to maintain a competitive edge by learning career, if just holding the learn to eat a craft to old mentality to do this line, You may be out sooner than you think.

As independent developers, especially the rain creek think his time can be completely free, don’t have to work overtime, in the aspect of work and family balance is better than working for the company, so to speak too much, of course, the other side of the independent development is the need to take more pressure and risk, but also have enough self-discipline, so not for everyone, but for him, He is very satisfied with the present state of life.

ArchSummit global Architect Summit will be held in Beijing International Convention Center on December 7-8, focusing on topics such as micro-service financial architecture, micro-service architecture, data infrastructure platform construction, short video architecture, blockchain, information privacy security and so on. Technical experts from Alibaba, Netflix, Baidu, LinkedIn and others were invited to share.

30% discount registration, immediate reduction of 2040 yuan, any questions welcome to consult Lachel- Ash, ticketing manager, tel/wechat: 17326843116.