@rstoenescu What if I have a bunch of other things on the server? Including other PWAs? The PWA app needs a place of its own so it can play nice with others.

create a separate sub-domain?
different names for the various service workers?
other?

This did work in .15

I am having some issues upgrading my PWA app from .15 to .16

I got a little frustrated thinking it may be something with my app itself, so I created a brand new PWA app from the new CLI and still have issues with the service worker path.

The app works fine, but the service worker never gets registered/updated

Basically here is my error,

Error during service worker registration: TypeError: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.

my app is upload to a subdirectory on my domain, so the service worker is located there.

https//mydomain.com/myapp/service-worker.js

but the fresh PWA is trying to register a service worker located at the root & not the subdirectory

https://mydomain.com/service-worker.js

is this a bug? or am I missing a configuration option for the new PWA/workbox?

before I was using the build -> publicPath to control where all the files should be, but it seems like publicPath should be empty now.

Thanks @rstoenescu
I know it is just a material design thing & I really hate to deviate from standards and make special cases. My users were just asking for it. I had already started to inspect the CSS and overwrite things, I just figured I would ask to see if there was a “better” way.

I have stacked labels on my forms and my users (poor eyesight & looking at screens in the sun) are complaining that the labels are too small and faint. Is there an easy way to change the size and weight of the font of the labels?

Preferably using a scoped stylus/css class name that I can add to the q-fields I want bigger.

I don’t really want this to be global, but would if you have a way with Stylus Variables, it would probably work for me. Even if it is global.

I am using q 0.15.6 with material design.

@rstoenescu I think this may be a bug with the quasar cli and the sw-precache-webpack-plugin. I have a similar problem and started tracing through the quasar source code and found.

line of 401 of https://github.com/quasarframework/quasar-cli/blob/0eab359c1741f6d6304fcd5359b592c628b35128/lib/build/webpack-config.js
we can see that
stripPrefix: cfg.build.distDir + ‘/’

in theory the stripPrefix should remove the ‘dist/pwa-mat’, so it doesn’t end up in the service worker, but it doesn’t

I tried adding my own stripPrefix property to the ‘quasar.conf.js’, but obviosly that won’t help, because the q-cli is hard coding the stripPrefix based of the cfg.build.distDir

the docs state that the distDir should default to ‘Relative path to project root directory. Default is ‘dist/{ctx.modeName}-{ctx.themeName}’. Applies to all Modes except for Cordova.’ http://quasar-framework.org/guide/app-quasar.conf.js.html

line 225 of this file seems to prove this https://github.com/quasarframework/quasar-cli/blob/16df4efe6555e1a8c64c05357468bb72d57411c4/lib/quasar-config.js

HOWEVER the stripPrefix doesn’t seem to be working with the quasar defaults.

If I manually add ‘distDir: ‘dist/pwa-mat’’ to the build in quasar-config.js everything seems to work as expected.

I my case, i don’t really want to manually add the distDir to my config, because we are building for a couple different environments.

any luck with this? i am doing something similar, but when i have the vuex strict, i get the following error.

[Vue warn]: Error in callback for watcher “function () { return this._data.$$state }”: “Error: [vuex] Do not mutate vuex store state outside mutation handlers.”

I really like using chips for with my q-select, but it misaligns my forms and makes things look “off”. Any tips to help with this?

@rstoenescu said in need quasar form components to emit on change/input:

triggered whenever the model changes

One thing that is driving me a little crazy with Quasar is the @change is triggered differently than traditional Vue.

see this jsfiddle
https://jsfiddle.net/daveline/dr5fzcrr/

notice how the input is triggered as you type
notice how the change is triggered as you click off the component (even if the model has changed)

if you replace the input with an q-input, the input AND change will be triggered as you type.

QInputFrame isn’t really documented, but I have noticed that is used everywhere behind the scenes. Any concerns with me using QInputFrame in my own component?