Skip to content
#

progressive-web-app

pwa logo

Progressive Web Apps start with a traditional web site/application and progressively enhance with modern features. When sites are secure they can leverage ServiceWorkers to provider users with offline support, Push notifications can help re-engage users, and Web App Manifests let users install PWAs alongside native apps.

Here are 1,511 public repositories matching this topic...

workbox
jeffposnick
jeffposnick commented Feb 17, 2021

For background, see https://stackoverflow.com/questions/66229902/

We can add a question to workbox wizard that checks to see if the developer has a web app manifest with a start_url that uses a query parameter, like homescreen=true or something else other than utm_ or fbclid, and if so, sets up the ignoreURLParametersMatching parameter for them.

JustFly1984
JustFly1984 commented Jan 14, 2018

The issue I'm experiencing is pretty annoying.
I'm trying to optimize my first byte, by turning off compression, and gziping everything by webpack with CompressionPlugin. The issue is that it doesn't compress service-worker.js produced by sw-precache-webpack-plugin.

I understand the reason why: service-worker.js should cache all chunks produced by webpack after CompressionPlugin compress

pwa-asset-generator

Automates PWA asset generation and image declaration. Automatically generates icon and splash screen images, favicons and mstile images. Updates manifest.json and index.html files with the generated images according to Web App Manifest specs and Apple Human Interface guidelines.

  • Updated Feb 18, 2021
  • TypeScript