forum.getkirby.com
Vue - Lessons learned
Excerpt
## Vue Cli is not for me I have also tested Vue Cli. It took a while to install and it added 100 Mb to my disc. It also added a structure and a user interface to add modules like Sass etc. Everything worked, but I felt it was too much magic for my taste. Something like WordPress or maybe even Skynet was taking over. I wanted to regain control, so I ended up using plain javascript files and Gulp to bundle and compress my javascript and my scss files. … Another reason was that I ran a `v-if` on `data.length` on my parent component. It used a big data object with hundreds of nested objects. When I changed a value inside the data object, it needed to reload everything again for some reason. I saw someone on Stackoverflow having the same problem. My solution was to cache the length into another variable that only was triggered when created. Both of the issues I was dealing with was due to the fact that it was too much reactivity involved. It’s often the strength of Vue but can cause problems as well.
Related Pain Points
Vue application performance bottlenecks
6Vue applications encounter multiple performance issues including large component trees with frequent updates causing slow rendering, unnecessary re-renders from reactive data mismanagement, heavy initial load times from large bundles, and memory leaks from improperly managed event listeners or unused refs.
Build Configuration and Import Complexity
5Understanding Vue's build setup and variant imports (runtime vs. compiler) is crucial but non-obvious; misconfiguration leads to blank pages and errors, requiring developers to master build tooling details.