I prefer a polished late release to a buggy early release…

Interesting topic. Note that the “theme” word is misleading as Quasar use it for material or ios builds. “color scheme” would be more appropriate…

I moved back from yarn to npm 5.x (included in node, lock file by default, fast). npx is the icing on the cake:
https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b

You can create a “foo” empty project with 0.13 and another “bar” empty project with 0.14 and see the changes with a diff tool like Meld (also in Ubuntu repos). It really helped me to migrate smoothly.

@a47ae templates usage is the number one problem Vue-CLI 3 was created to solve: https://github.com/vuejs/vue-cli/issues/589

The short list of Vue CLI 2 templates was mainly about build systems. They are now replaced by a plugin-based configuration of webpack (a little bit like the Quasar’s extendWebpack function btw, except no templates are used at all)

@terry Launch is for browsers. Instead why don’t you simply create a npm script in package.json, such as for instance:

"dev": "quasar dev -m pwa",

and then in vscode Task > Run Task… and chose npm: dev

@leopiccionia thank you so much.

1. you’re right for Pug, I forgot it was automatic
2. Great! Right now I’m customizing the build.extendWebpack function of quasar.conf.js to add loaders to my Vue single component files. I guess the documentation will talk about that.

I’m feeling better now…

testing it right now!

Next one in London: http://vuejs.london/

Sometimes a single component can be used for several pages (i.e. routes). That’s the beauty of routing
Do you know nuxt? https://nuxtjs.org/guide/routing

@al1_andre Sounds like an issue with background sync.

Unfortunately, for now, background sync only works with Chrome.

@mesqueeb I just saw your question. I’m using Firebase so I’m simply using Firebase offline persistence features.

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.

I really needed Ionicons v4. Thanks Razvan!

Also maybe this is an issue as Cordova uses WebView if I’m right: https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html

@driedler I took the PWA train months ago. But I remember I had some issue with Cordova and firebase OAuth. I had to call auth.getRedirectResult() at the created hook of my component where the authentication takes place, because the app was destroyed before sign-in was complete, so a new app was created after authentication and getRedirectResult() had to be called asap.

Hope it helps…

Amazing

https://medium.com/@firt/progressive-web-apps-on-ios-are-here-d00430dee3a7

I think this will be fixed in 0.15.8: https://github.com/quasarframework/quasar/issues/1783

Same issue here. Wasn’t here in 0.15.4. When you land on or refresh the page you can see the drawer hiding like a mouse when you turn the light on in a garage.

@Max no-hide-on-route-change just prevent the drawer from hiding when changing routes. But here the drawer hides at app startup.