@rstoenescu I’ll give that a try.
In that case what does Quasar.Start do by accepting a function that wraps of new Vue instance?
That seems like the major difference from a vue only app. Will that mess with any other packages I try to use?
I kinda expected quasar to just be a component library I import and then .use but this is something more.
One other issue I see having is what goes on the in build and config directories. The vue webpack2 template has them but quasar webpack2 template has slightly different files and likely different content in webpack (base,dev,prod) confs. Since I’m a noob with webpack merging those could be painful since I really am unsure about all that webpack is doing. So are the quasar files likely a superset of those in the corresponding vue webpack2 template? Need some input on dealing with that piece.
The /src stuff should not be an issue and must be re-factored for using quasar components anyway.