@ciw1973 yea, today i’m generating whit backend and yes i prefer this way.
But when people navigate in the docs of a framework, they have expectations. This feature is very good to sell the FW.
I just want quasar get bigger .

As @a47ae said I was referring to the documentation page, sorry for being unclear. I took a look and I was surprised to see some ejs templates in there.
Using the click event will break the semantics of the link element. I ended using an a tag with all the button classes except q-btn. I think that offering an element (or set of directives ) to style a link to look like a button is something reasonable, I saw it at several places

@Suraj Sorry my bad, I was looking at the output of yarn outdated which obviously lists Vue as outdated and thought it would also update Vue with a yarn upgrade.
Also in earlier versions of Quasar (pre 0.14) the Vue dependency wasn’t locked with the tilde

Ok so it turns out quasar build does update my cordova app as well without modifying my 2 files. Thanks to everyone that helped out. And thanks for the Makefile script, I’m suerly gonna check it out and use it!

Ok, there should be something weird with the cache after the build process. I manually updated the manifest file directly on the gh_pages branch to point to https://www.danielorodriguez.com/JSONTools/ and now I get 100 of 100 on the PWA check and the service worker works fine.

I’ll try again to set it on the master branch and let it build to see if it happens again.

@rstoenescu could we have a prop for that in all animated components please?
e.g. adding no-animation to a component would do that css override (or anything else appropriate internally to forfeit the animation effect)

or maybe animation="none" if you plan on later allowing custom animations to be set through that same prop ( /wink /wink /nudge /nudge )