@rstoenescu The combination of Vue.use( Quasar ) and WebPack2 seems like working against each other, I mean …

If all components are registered into Vue core as global components, then WebPack2 can shake all the tree’s it likes to, these components will not be seen as dead leaves, as noone can check if they have been used inside some templates ?

importing components just as you would with any Vue components. On demand, starting with root component

Is there any other problem with this, other than possible duplication of code for the developer? ( I think I remember you mentioning this is what is being avoided with the global implementation of components.)

And, what if I want to introduce new components outside of the Quasar built ones? Would I have to refactor them to fit into the Quasar system, to then introduce them globally in some way?

@s.molinari Haven’t decided yet on the best way to go, so the design is in progress. No duplication will occur if we go with registering Quasar components on global Vue on main.js. Importing Quasar components works just the same as importing ANY other components. We’re using Webpack for this, so nothing specific between importing a Quasar component or other components.

@AhsanAbrar Hi, like Scott indicated, the framework is pretty stable and usable as it is now. v1.0 will only mean a few features more and (probably) some very minor API changes that will be easy to upgrade to.