That is ugly! I would probably do something on mounted (and upgrade as soon as possible to v0.16) mounted () { console.log('The instance has been mounted') // Note that mounted does not guarantee that all child components have also been mounted. // If you want to wait until the entire view has been rendered, you can use vm.$nextTick // inside of mounted: this.$nextTick(function () { // Code that will run only after the // entire view has been rendered }) }, Here is a great resource for you: https://github.com/LeCoupa/awesome-cheatsheets/blob/master/frontend/vue.js

@limjackson SSR work is being done with 0.17 (which is currently in a prerelease) and yes, hopefully it should all just work.

@Hawkeye64 @silentcoast - I wrote about this on a quasar issue: https://github.com/quasarframework/quasar-cli/issues/122#issuecomment-391266544 the easy fix is to up the amount of memory node has available: $ NODE_OPTIONS=--max_old_space_size=4096 DEBUG=v8:* npm run dev:pwa where dev:pwa is “dev:pwa”: “quasar dev -m pwa”, in package.json

Hi @mymacy myMethod() is placed here : export default { components: {}, data () { return {} }, methods: { myMethod () {} } } And i call it with a click for example :). Hope it helps !

@Jams I suggest you re-read the Layout section (with all its pages) in docs. Also look at the source code for Play examples. You’ve missed a couple of important things, like the “view” QLayout prop. Also, placing QPageContainer right under the QLayout works, but it’s not quite efficient (in your specific case). I recommend wrapping only <transition> with its <router-view>.

For babel polyfill, just tamper with the .babelrc – mind that for v0.16+ u’re on Babel 7, not 6

@marcelo docs are always updated when a new version is released. maybe a browser cache issue?

I’m going full PWA so I do not need Electron nor Cordova. I use vue-cli 3 with a customized Quasar UMD build (removed unneeded components and css with a bit of metaprogramming) and with a custom script at startup I can dynamically load different themes depending on the platform. The more I use vue-cli the more I think quasar-cli is amazing because it really hides a lot of complexity from developers.

Hello again! I’m afraid that this issue might have solved itself. I realized I accidentally lied about the <q-popover> being a direct child of <q-btn>, because it was in a different component (of which the QPopover was the root element). Changing this and putting the <q-popover> directly in the parent component solved the issue, so I thought this was the problem; but when I reverted back to it being separate, it actually still works and I can’t reproduce the error.

I’ve been told by a developer that in his case using lazy loading solves this webpack issue.