In https://github.com/vuejs/vue/releases/tag/v2.5.0
Provide/Inject
support providing default values for injections (#6322) 88423fc
So, is it fixed or not ?

I was looking at https://www.youtube.com/watch?v=rn97hCNQsKI practical part starts at minute 6:30
Sean Larkin (a maintainer of webpack) recommends to use code splitting ALWAYS on routing.

https://github.com/quasarframework/quasar-template-pwa
Working in progress …

Digging into forum I found @s.molinari saying “Quasar is PWA ready. Only the wrapper is missing.” http://forum.quasar-framework.org/topic/241/excellent-work/4
Any info about this in 0.14 or in roadmap after full release ?

@JDrechsler this is a complementary info https://webpack.js.org/guides/lazy-loading/
I am glad that you solve it, I think it is much better to move this to low level layer, as far as I see is webstack.

@paul totally agree … I do not see too much freedom and control in native apps development, Cordova, Weex … patching situation … mmm.
Back to the roots, let stay in web-mode, claim app control out of stores and use full device features.
To whom may concern, is there anything we can do to make Quasar PWA and SSR possible ?

@JDrechsler Ok I see but … what about webpack 3 ? At least you should do something like this https://alexjoverm.github.io/2017/07/16/Lazy-load-in-Vue-using-Webpack-s-code-splitting/

I am sorry if it has non sense but have you tried async component support for webpack 3 and vue js 2.4.0 ?
I know that 0.14 has issues with 2.4.0 and webpack 3 is a different animal
I think also it could be better to have lazy loading out of router app flow (to avoid constraint app routes and delay responses).
This is a very interesting challenge before to consider to move to SSR: to serve or consume code by context, needs and demand.

Well why not to go to progressive web apps ? Why not to push Quasar into PWA and SSR ?

We are passionated about v0.14 but hold your horses, first learn how new version works in depth, you will probably discover that your are dealing with a new framework to finally conclude that it is worth to rethink most of your ui app before to consider to upgrade from 0.13.
For me it is a major upgrade rather than a simple update.
I hope to be wrong but I do not see a clear upgrade path, a deep refractor is need, in some case it will push to rewrite components and app flow.
If one does not know well v0.14 and vuejs version behind and how to use it appropriately, the it will not be posible to estimate how much it will cost in time and work.
Any way sooner or later v0.14 will be the path so make space and be ready.