Getting started

Using PWA Fire Bundle

Download PWA Fire Bundle

Last updated on 20/06/18 Cache Google Fonts Offline Google Analytics

Download PWA Fire and from pwafire-bundle folder, upload the service-worker.js and manifest.json files to the ROOT folder of your project or website. Be sure to edit the service-worker.js and manifest.json file as in the guide provided below to fit your web app needs.

N/B: Make sure to make the configuration changes as documented.

Code to register the service worker

This is the first step to making your web app work offline. Copy and paste this code to your index file, eg just before the end of the body tag or in the head tag in html5

N/B : YOU NEED HTTPS : You can only register service workers on Websites, Web Apps or Pages served over HTTPS.

This code checks to see if the service worker API is available, and if it is, the service worker at /service-worker.js is registered once the page is loaded.
First, we need to check if the browser supports service workers, and if it does, register the service worker.

    <!-- register service worker -->

          if ('serviceWorker' in navigator) 
          window.addEventListener('load', function() {
            .then(function() { console.log("Service Worker Registered, Cheers to PWA Fire!"); });
    <!-- end of service worker -->

Using the web manifest

Add a link tag to all the pages that encompass your web app, as follows;

      <!-- start of web manifest -->
      <link rel="manifest" href="/manifest.json">
      <!-- end of web manifest -->

Service Worker // service-worker.js config

NOTE : Rich offline experiences, periodic background syncs, push notifications—functionality that would normally require a native application - are now being built on web. Service workers provide the technical base to which all these features rely on.

A service worker is a script that your browser runs in the background, separate from a web page, opening the door to features that don't need a web page or user interaction.
Follow the steps as commented in the code below in order to correctly configure the service-worker.js file.
        // A project PWA Fire written. All writes reserved 2018.
        // Author : Maye Edwin
        // after a service worker is installed and the user navigates to a different page or 
        // refreshes,the service worker will begin to receive fetch events
        self.addEventListener('fetch', function(event) {
        event.respondWith('cache').then(function(cache) {
        return cache.match(event.request).then(function(response) {
        console.log("cache request: " + event.request.url);
        var fetchPromise = fetch(event.request).then(function(networkResponse) {           
        // if we got a response from the cache, update the cache                   
        console.log("fetch completed: " + event.request.url, networkResponse);
        if (networkResponse) {
            console.debug("updated cached page: " + event.request.url, networkResponse);
              cache.put(event.request, networkResponse.clone());}
                return networkResponse;
                  }, function (event) {   
        // rejected promise - just ignore it, we're offline!   
                  console.log("Error in fetch()", event);
        'cache').then(function(cache) { 
        // our cache is named *cache* in the above
                  return cache.addAll
        //cache.addAll(), takes a list of URLs, then fetches them from the server
        // and adds the response to the cache.           
        // add your entire site to the cache- as in the code below; for offline access
        // If you have some build process for your site, perhaps that could 
        // generate the list of possible URLs that a user might load.               
                '/', // do not remove this
                '/index.html', //default
                '/index.html?homescreen=1', //default
                '/?homescreen=1', //default
                '/assets/css/main.css',// configure as by your site ; just an example
                '/images/*',// choose images to keep offline; just an example
        // Do not replace/delete/edit the service-worker.js/ and manifest.js paths below
        //These are links to the extenal social media buttons that should be cached;
        // we have used twitter's as an example
        // respond from the cache, or the network
          return response || fetchPromise;

Node modules production ready service-worker.js

If you are using node modules for your web application, then we got your back to help you get started. We are going to use workbox. Read more on workbox and latest releases here.

Create an empty js file; service-worker.js in your source root. In the empty source service worker file, say src/service-worker.js ; add the following code snippet: Go through the comments.

          if (workbox) {
          console.log(`Yay! Workbox is loaded ! Cheers to PWA Fire🎉`);
           } else {
           console.log(`Oops! Workbox didn't load 😬`);
The importScripts call imports the workbox-service-worker.js library from a Content Delivery Network (CDN). Once the library is loaded, the workbox object gives our service worker access to all the Workbox modules.

The precacheAndRoute method of the precaching module takes a precache "manifest" (a list of file URLs with "revision hashes") to cache on service worker installation.

Create an empty sw-config.js file in your project's root folder. Add the code snippet below to it; configure to add which files you want to precache.

       module.exports = {
       "globDirectory": "build/", // The base directory you wish to match globPatterns against, 
       // relative to the current working directory.
       "swSrc": "src/service-worker.js", // The path and filename of the service worker file that will be created by the build process.
       "swDest": "build/service-worker.js", // The path to the source service worker file that can contain your own customized code,
       // in addition to containing a match for injectionPointRegexp.
      "globIgnores": [
Open your package.json and update the build script to run the Workbox injectManifest command. Add workbox injectManifest sw-config.js infront of your-build-process-task . The updated package.json should look like the following:

          "build": "your-build-process-task workbox injectManifest sw-config.js"

NOTE : workbox-cli ; is a command-line tool that allows us to inject a file manifest into a source service worker file.

The precacheAndRoute call in build/service-worker.js has been updated. In your text editor, open build/service-worker.js and observe that your files to cache are included in the file manifest.

Done! Now you will have your production-ready service workers when you build your web app! Let's build! If you get any bug, report it here

OPTIONAL : Want offline analytics for your offline PWA? No problem. Add the code snippet below to src/service-worker.js


OPTIONAL : Wish you could rely on Google Fonts being available offline after the user has visited your site? Add a quick rule to serve them from the cache.

      new RegExp('^https://fonts.(?:googleapis|gstatic).com/(.*)'),
Get started generating your production ready service worker for gulp in this codelab here
Get started generating your production ready service worker for webpack in this codelab here

Web Manifest // manifest.json config

Configure/edit the background and theme colors, display type, the Web App short name, the Web App name, icons size (keep icon sizes as specified below) and your icon/logo paths. Also state the img type eg image/ico or image/png.

Released 25/05/2018

Or maybe you could use our NEW Web Manifest Genarator to genarate the manifest.json file. Be among the first to try this tool out! Share out to your comunity.

Leave the start url as recomended though this can be anything you want; the value we’re using has the advantage of being meaningful to Google Analytics.

Configuring the manifest.json file helps you to specify how you want your web app to look like when launched on the device.
Configure the manfest.json file as directed above in order to fit your web app needs.

          "background_color": "#fff",
          "display": "standalone",
          "theme_color": "#fff",           
          "short_name": "PWA Fire",
          "name": "PWA Fire",
          "description": "description or purpose of your progressive web app",
          "lang": "en-US",
          "icons": [
          "src": "images/pwafire48.png",
          "type": "image/png",
          "sizes": "48x48"
          "src": "images/pwafire96.png",
          "type": "image/png",
          "sizes": "96x96"
          "src": "images/pwafire192.png",
          "type": "image/png",
          "sizes": "192x192"
          "src": "images/pwafire512.png",
          "type": "image/png",
          "sizes": "512x512"
          "start_url": "index.html?launcher=true",

In the head tag, add theme color to all your pages as shown in the code below; You could use the same theme color as in the manfest.json file.

        <!-- theme-color -->
        <meta name="theme-color" content="#fff" />
        <!-- end-theme-color -->

What's next?

Donate a Star and Contribute in any way. Be sure to Follow and use Project PWA Fire. If you use PWA Fire kindly let us know via or JUST simply Tweet us


Copyright PWA Fire, 2018. Licensed under an MIT license.