What are the disadvantages of vue-cli?

Question

Vue.js

Lately, I've encountered some disdain for vue-cli several times.
Who can explain on specific cases what is wrong with it? what things can't be done?
Interesting opinion in the context of medium and large projects.
Personally, in my experience, I have never come across a situation where vue-cli would prevent me from doing something.
But I regularly hear how people have problems with self-written webpack configs

Answer 1

In the context of small and medium-sized projects, vue-cli (hereinafter I will mean other clients of other frameworks) has some pluses - in a conditional 5 minutes you get a typical config that you can expand with your plugins and get a working build.
A large project assumes that:
1) a non-standard assembly, several entry points with their own config and other fun amenities may be required
2) a specialist works on the project who knows how the assembler works and can write the necessary config for it himself from scratch
3) for clients have their own configs that you need to learn how to use in addition to the collector configs. Not everyone likes to learn extra things
And here the problems begin - the client generates its own config, and adds to it what you added. At the same time, what he eventually generated there was not particularly convenient to look at. As a result, everything turns into a situation "what else did this tool generate there, I'm tired of interrupting the rules."
If the project fully fits the standard vue-cli config, there is nothing wrong with using it.
The angular cli is better in this regard - there you can choose what to do with the custom config - mix it with the standard one, or replace the standard one with it. Vue, a few I know, doesn't have that option.
PS my vue-cli can't properly build a freshly created project with vuetify, I have to downgrade the sass-loader version. For such "chips" separate rays of goodness.