Is using vue-cli and vue-cli-service a bad practice?

Question

I'm building an application with vue-cli and I see that webpack config is not explicitly defined in my repo. It's hidden from us (although it can be changed). Default run dev script by vue-cli also use vue-cli-service instead of webpack.

I'm a questionning myself about the consequence of this.

Are we losing control over the webpack config?
Does new version could modify the base hidden config without us knowing it ?
Are vue-cli taking too much space and break some decoupling principle (since it will be more difficult to change from webpack to another bundler for example) ?

Thanks in advance.

Regards

(English not my primary language, sorry)

tony19 · Accepted Answer · 2022-07-15 23:19:34Z

2

No modern framework's CLI (including Vue) is going to operate not according to best practices.

You can read on how to work with Webpack in Vue here: Link.
New versions with breaking changes are documented like so: Link.
An application built on any framework will depend on that framework, regardless of CLI use. Configurations built from the CLI can always be changed manually.

edited Jul 15, 2022 at 23:19

tony19

140k23 gold badges281 silver badges354 bronze badges

answered Jan 3, 2020 at 2:07

Tanner

2,4411 gold badge15 silver badges23 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Is using vue-cli and vue-cli-service a bad practice?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related