The problem of quantity and performance of vue components

imagine having two components
componentA, componentB

componentA is a ul , and
componentB is called li

< componentB vsway for = "i in list" / >
(while this list is an array of more than 100)
v-for the same number of componentB,

is there a big god who knows that there are any doubts about the performance of a large number of generated components such as v vendor ue? Maybe it"s better not to break it up into widgets?
wants to know how vue handles this, and whether a large number of vue nodes will be generated at compile time (is that so?) , causing performance to slow down?

Webpack javascript vue.js

Mar.12,2021

take a look at the lifecycle of Vue. In fact, all components mount Mount , render, and generate virtual DOM nodes. The compilation of components and the transfer of data between components naturally take time, so the functions that can be implemented in a component should not be separated as far as possible.

1. First of all, the purpose of encapsulating the component is to reuse and improve the maintainability of the code. If you have simple code in your li, there is no need to encapsulate it. If the logic is more complex, it can be encapsulated into a component
2. Second, the efficiency will certainly decrease after it is encapsulated into a component, but it will only go through the complete life cycle when it is loaded for the first time, and the impact on efficiency will be ignored if later updates are made
3. Third, if you have 100 or more li, do you want to consider paging loading? it is impossible to load so many

at one time.

Previous: How webpack shuts down strict mode

Next: Synchronize asynchronous, blocking and non-blocking

ProxyTable satisfies two conditions at the same time (one of which is non)
satisfies both the beginning of api and the need to forward to aaa, api order to bbb. api : { target: http: dev.api.aaa.cn , changeOrigin: true }, api order : { target: http: dev.api.bbb.cn , changeOr...

Node.js webpack javascript vue.js

Mar.04,2021
Npm run dev was successful 95% of the time, but the page could not be opened.
A sudden problem with vue-cli scaffolding today after npm run dev, there was a problem, and the final result was also successful, but the page could not be opened at all excuse me, what is the reason for this? has anyone encountered it ...

Node.js webpack javascript vue.js vue-cli

Mar.09,2021
Vue-cli introduces vux to report errors?
introduce error reporting ...

Vux webpack javascript vue.js

Mar.11,2021
How to package all js and css into a js file in vue-cli
how to package all js and css into a js file in vue-cli, and if not, how to package app.js manifest.js vendor.js into a file ...

Webpack javascript vue.js

Mar.20,2021
In nuxt.js: will an error be reported when src parses the value in data?
export default { data: { in js imgUrl:require(this.placeImg) } props: [ placeImg:{default: ~assets img 3339.png } ] } this won t work. What it means on the Internet is that require can t parse variables. Is there any way to solve this? ...

Webpack javascript vue.js

Mar.22,2021
Webpack loader installs an error on the server
cnpm image-webpack-loader gifsicle build:webpack g I installed a libpng library on the server, but two more dependencies were not installed. ...

Npm linux webpack javascript vue.js

Mar.14,2022