Just created an issue in github while I wasn’t aware of this post. But I’m glad there’s a discussion about it, because few hours ago (after Razvan even replied to this topic), Evan announced remote presets, which I think it was the missing feature for all this to be even taken in mind.
Besides of all the drama, I quote @Vinkman
It concerns me that I’m writing a Quasar app instead of an Vue app, as I might want to include some vue cli 3 plugin in the future, which I cannot do when using the Quasar CLI. It isn’t unreasonable to think there might be usefull plugins released that way. It’s a way of futureproofing our work here, because in the end, we’re developing a Vue application.
And regarding to this:
If, for some reason, you decide to go against recommendations and just throw out the window 50% of what Quasar can do for you…
By creating a new remote preset for vue-cli, we can still use webpack for electron, cordova, PWA, SPA, etc…
Not a single piece of functionality is lost by applying current quasar-cli functionality into a vue-cli 3 preset. And in my humble opinion, you’re gaining a lot from letting your users stick with what they know from vue docs/courses (and ofc, vue’s CLI features, such as plugins).
Sooner or later, there will be plugins/presets for pretty much everything that quasar-cli offers. But that’s just my opinion.