We’ll be using Quasar CLI to develop and build a PWA. The difference between building a SPA, Mobile App, Electron App, PWA or SSR is simply determined by the “mode” parameter in “quasar dev” and “quasar build” commands.

In order to build a PWA, we first need to add the PWA mode to our Quasar project:

$ quasar mode add pwa

If you want to jump right in and start developing, you can skip the “quasar mode” command and issue:

$ quasar dev -m pwa

This will add PWA mode automatically, if it is missing.

A new folder will appear in your project folder (which is explained in detail on the Configuring PWA page):

.
└── src-pwa/
    ├── register-service-worker.js  # (or .ts) UI code *managing* service worker
    ├── manifest.json               # Your PWA manifest file
    └── custom-service-worker.js    # (or .ts) Optional custom service worker file
                                    #               (injectManifest mode ONLY)

All the files above are going to be detailed in the next pages, but the high overview is:

• The register-service-worker.[js|ts] file is part of the UI code and communicates with the service worker.
• The manifest.json is the PWA manifest file.
• When using InjectManifest, you can write your own custom service worker (custom-service-worker.[js|ts]).

Should you want to use different filenames, you can do so by editing /quasar.config.js:

// quasar.config.js

sourceFiles: {
  pwaRegisterServiceWorker: 'src-pwa/register-service-worker',
  pwaServiceWorker: 'src-pwa/custom-service-worker',
  pwaManifestFile: 'src-pwa/manifest.json',
}