Service Worker Toolbox
A collection of tools for service workers
Service Worker Toolbox provides some simple helpers for use in creating your own service workers. Specifically, it provides common caching strategies for dynamic content, such as API calls, third-party resources, and large or infrequently used local resources that you don't want precached.
What if I need precaching as well?
Then you should go check out
sw-precache before doing anything else. In addition to precaching static resources,
sw-precache supports optional runtime caching through a simple, declarative configuration that incorporates Service Worker Toolbox under the hood.
Service Worker Toolbox is available through Bower, npm or direct from GitHub:
bower install --save sw-toolbox
npm install --save sw-toolbox
git clone https://github.com/GoogleChrome/sw-toolbox.git
Register your service worker
From your registering page, register your service worker in the normal way. For example:
As implemented in Chrome 40 or later, a service worker must exist at the root of the scope that you intend it to control, or higher. So if you want all of the pages under
/myapp/ to be controlled by the worker, the worker script itself must be served from either
/myapp/. The default scope is the containing path of the service worker script.
For even lower friction, you can instead include the Service Worker Toolbox companion script in your HTML as shown below. Be aware that this is not customizable. If you need to do anything fancier than register with a default scope, you'll need to use the standard registration.
<script src="/path/to/sw-toolbox/companion.js" data-service-worker="my-service-worker.js"></script>
Add Service Worker Toolbox to your service worker script
In your service worker you just need to use
importScripts to load Service Worker Toolbox:
importScripts('bower_components/sw-toolbox/sw-toolbox.js'); // Update path to match your own setup.
Use the toolbox
The team behind
sw-precache have been busy creating Workbox, which is a collection of libraries and tools that make it easy to build offline web apps. It’s a joining of sw-toolbox and sw-precache with more features and a modern codebase.
What does this mean for sw-toolbox?
For now, it means we’ll continue to support both
sw-precache with critical bug fixes and releases. However, non-critical bugs are unlikely to be addressed.
Should you switch to Workbox?
We would recommend Workbox for new projects, but there is no immediate need to switch if
sw-precache meets all your needs in your current project. We will announce a deprecation plan for these modules once Workbox has feature parity with
In the meantime, you can get updates by following @workboxjs.
Copyright 2015-2016 Google, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.