Custom ServiceWorker config

1.0.0 added Progressive Web App support, is it possible to support custom config in near future? I really don’t want to eject just to add runtime caching configs 😄

[dsgh]

@Timer I just updated to the newest version, and tried to use the new PWA support as well, and there seems to be an issue with Firebase auth. Firebase auth uses the /__/auth/handler path, which seems to be ‘cached’ by the default config (returning the app itself). So for now I had to abandon the idea. Here’s what I believe to be a related issue, for the polymer project: https://github.com/Polymer/polymer-build/issues/35#issuecomment-245981301

[jeffposnick]

There are definitely use cases where folks might want something other than the default configuration. I tried to choose default configuration options that are, in general safe, with the understanding that developers who need to make changes will go through the eject flow and modify the configuration (which seemed to in keeping with the overall approach for this project).

I don’t know how common it is for servers to use the /__ prefix for “special” URLs that are server-rendered and shouldn’t be fulfilled via the locally cached content, but adding in the configuration option

{
  navigateFallbackWhitelist: [/^(?!\/__)/]
}

would account for them. Doing so would be unlikely to break anyone, and it would accommodate some of the folks upthread without forcing them to eject.

As for the questions about configuring runtimeCaching, I tried to cover that in item 7 of this guide. There’s no single configuration option that’s likely to work for everyone, so using the eject flow would be the way forward.