Ch13 - Converting to a PWA #106
Conversation
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
This reverts commit 47f67e6.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
|
FYI - this PR's commit history is a bit of a mess b/c I at first failed to properly get my hand-crafted PWA manifest output into the dist folder along with icons and links. So I tried using this package that can generate and inject the manifest. Simple, right? wrong. Unfortunately, the maintainer of this project isn't... well, maintaining the project any longer, and the last update was a couple years ago prior to the release of WebPack v5.0, which contains a number of breaking changes from the previous version. All of which goes to say that I wasn't confident that using a generated manifest was a great approach, then I tried the CopyFilePlugin approach and it seems to work exactly as needed. |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-river-0b8108510-106.centralus.azurestaticapps.net |
Commits cover changes needed to convert the web application into a Progressive Web Application. Uses the workbox webpack plugin to generate and emit a ServiceWorker that will allow the PWA to run offline with cached assets.