Jekyll Service Worker

Back in 2017 when I was originally putting this new blog together with Jekyll I made a point of integrating a service worker with the build process. Generating the required urls to cache using liquid tags and embedding these within the URL’s to be cached on service worker activation can be included.

Caching built pages from jekyll

In a previous post I show a simple service worker setup where some URL’s are specified for caching. When building the site with Jekyll, it is good to not have to keep a list of every page up to date in the service workers set of routes to cache, so we can instead use liquid within our service workers file to generate the routes we need to cache at build time.

{% capture asset_urls %}
{% for page in site.html_pages %}
'{{ page.url | remove: '.html' }}',
{% endfor %}

{% for post in site.posts %}
'{{ post.url }}',
{% endfor %}

{% for file in site.static_files %}
{% if file.path contains '/images' or file.path contains 'manifest' or file.path contains 'css' %}
'{{ file.path }}',
{% endif %}
{% endfor %}
{% endcapture %}

var SITE_NAME = '{{ site.url }}-site'
var CACHE_NAME = SITE_NAME + '-{{ site.time | date_to_xmlschema }}';
var urlsToCache = [
  {{ asset_urls | normalize_whitespace }}

The above script tracks pages which are our main routes like / and /contact. It also tracks each post like the one you are reading right now and adds it to the list. Finally it also adds static files, like images and other Jekyll pages without front matter that are not processed.

The setup also uses {{ site.time | date_to_xmlschema }} to keep our cache name unique each time we rebuild the site.

var CACHE_NAME = SITE_NAME + '-{{ site.time | date_to_xmlschema }}';

Currently some static resources need to be added manually with the above setup, so a few resources are included in the list already.

var urlsToCache = [
  '/manifest.json',     // manually added
  '/js/validate.js',    // manually added
  '/css/main.css',      // manually added

Installing the generated routes

These routes are injected inside the declared variable urlsToCache and then when we go to cache these URL’s with a service worker we pass these urlsToCache to the install step and they are added to our cache.

// Perform install steps
self.addEventListener('install', function(event) {
        .then(function(cache) {
            return cache.addAll(urlsToCache)

The install step inserts these resources into the browsers cache and subsequent loads of these resources intercepted by the service worker will use the cached asset over reaching out to the network, so the site will start working offline.

jekyll serviceworker liquid
Share this post on Twitter