Thanks, @rstoenescu.

I’ve got my service worker going using the copy-webpack-plugin. I added this to my webpack.base.config.js:

  var CopyWebpackPlugin = require('copy-webpack-plugin')

and in the list of plugins near the bottom of that file:

new CopyWebpackPlugin([
  {
    from: 'root/'
  }
])

Beside src folder, I have a new folder that I called root. All the files in that folder end up in the root of the dev and build outputs.

To use them, the index.html file has:

and to get OneSignal going, add their code to themain.js file

I’m actually using the OneSignal service worker along with my own. To do this, I edited both of the OneSignal files to add a reference to mine:

See https://documentation.onesignal.com/docs/web-push-sdk-setup-https for OneSignal information.

Done. See https://github.com/quasarframework/quasar/issues/464

It seems that the actual file does not need to be in the root of the site. That is a requirement for service workers, but not the manifest file.

So this works…

Index.html

 <link rel="manifest" href="/statics/manifest.json" />

and put the manifest.json file in the “src/statics” folder.

This doesn’t solve the problem of serving a file from the “root” for a service worker, but that’s another question…

With v0.16, where do I put a robots.txt file so that it gets put into the root of the server?

Glad to hear that the revamp will include this!

@lvaylet I simply rolled my own table with the rows how I needed them.

I think the build framework should do some of the optimizations found here: https://hackernoon.com/optimising-your-application-bundle-size-with-webpack-e85b00bab579

This is especially a problem with the “vendor.js” file. When I make a small tweak to some wording in my site, the user has to re-download this massive file, even though it did not change at all!

I suspect now that it is working, but didn’t do the expected substitutions.

For display: flex; it is outputting display: -webkit-box; rather than display: -webkit-flex;

After running Quasar build, all the files in the “dist” folder have new timestamps on them. Is there any way to tell the builder to retain the original file’s timestamp?

If I have a static image that doesn’t change, it should not have a new timestamp every time the project is built!

I needed to use Autoprefixer, since the CSS being output does not have prefixes applied. That is, “display: flex” should have “-webkit-display: flex” as well, etc.

When I looked at ‘css-utils.js’, I see that Autoprefixer is there!

Is there something that I need to do to activate this?

Done. See https://github.com/quasarframework/quasar/issues/464

Thanks! I’ll look into that after upgrading to version 12. (As per another thread at http://forum.quasar-framework.org/topic/180/load-roboto-font-from-cdn/5)

Another concern is whether changes to core files (as suggested in, for example http://forum.quasar-framework.org/topic/181/reduce-bundle-size/2) are lost when upgrading from 10 to 12. Do I need to be prepared to identify and re-apply all such changes?