Using Workbox without precaching

Published on

So far, this documentation has been big on precaching, often touching on the generateSW and injectManifest build tools. While there are plenty of good reasons to include precaching logic in your service worker, you don't have to use precaching to use Workbox.

Perhaps your project only needs runtime caching, or maybe you want a cleaner way to integrate service worker APIs, such as web push. These are cases when you won't want to use Workbox's build tools, and that's what is covered in this article.

When using a bundler

Bundlers are prominent in the web development landscape, and there's a good chance your project is using one. If this is the case, it's important to know that you don't need to use a bundler plugin (like workbox-webpack-plugin) if you aren't precaching anything. You'll be treating your service worker as a separate entry point in your application.


You'll need to make sure your chosen bundler supports the static import syntax. If you're using webpack, Rollup, Parcel, or esbuild, you're good to go!

In the root of your project's source directory, you'll create a service worker and use whatever Workbox modules your application requires. Here's an example without precaching, that sets up caching strategies for navigation and image asset requests in separate Cache instances instead:

// sw.js
import {NetworkFirst, CacheFirst} from 'workbox-strategies';
import {registerRoute, NavigationRoute, Route} from 'workbox-routing';

const navigationRoute = new NavigationRoute(new NetworkFirst({
cacheName: 'navigations'

const imageAssetRoute = new Route(({request}) => {
return request.destination === 'image';
}, new CacheFirst({
cacheName: 'image-assets'


From here, it's a matter of specifying this service worker as an entry point in your bundler of choice. Below are a few examples of how to do that in a few popular bundlers.


webpack accepts entry points in its entry configuration. There's a couple things to be aware of when using this approach:

  1. To ensure your service worker has the broadest possible scope, you'll want it to be output to the root of your output directory.
  2. You don't want the service worker to be versioned, as updates to it will generate new hashes that may result in multiple service workers being deployed on your website.

To satisfy the above conditions, a function can be passed to output.filename which examines if the current entry point being processed is the service worker entry point. Otherwise, versioned files are written to their normal destinations.

// webpack.config.js
import process from 'process';

const isProd = env.NODE_ENV === 'production';

export default {
mode: isProd ? 'production' : 'development',
context: process.cwd(),
entry: {
// Service worker entry point:
sw: './src/sw.js',
// Application entry point:
app: './src/index.js'
output: {
filename: ({runtime}) => {
// Check if the current filename is for the service worker:
if (runtime === 'sw') {
// Output a service worker in the root of the dist directory
// Also, ensure the output file name doesn't have a hash in it
return '[name].js';

// Otherwise, output files as normal
return 'js/[name].[contenthash:8].js';
path: './dist',
publicPath: '/',
clean: true

The above webpack configuration assumes you're using a recent version of Node that supports JavaScript modules, and has "type": "module" specified in your package.json file. Otherwise, you'll need to use CommonJS semantics.


Rollup is a similar situation to webpack, except multiple entry points are specified as separate configuration objects exported in an array:

// rollup.config.js
import { nodeResolve } from '@rollup/plugin-node-resolve';
import replace from '@rollup/plugin-replace';

// Plugins common to both entry points
const plugins = [

export default [
// Application entry point
input: './src/index.js',
output: {
dir: './dist/js',
format: 'esm'
// Service worker entry point
input: './src/sw.js',
output: {
file: './dist/sw.js',
format: 'iife'
plugins: [
// This @rollup/plugin-replace instance replaces process.env.NODE_ENV
// statements in the Workbox libraries to match your current environment.
// This changes whether logging is enabled ('development') or disabled ('production').
'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV || 'production')

Unlike webpack, Rollup doesn't have a mode configuration option that handles minification. You'll need to install and use rollup-plugin-terser to achieve this.


esbuild offers a straightforward command line interface:

npx esbuild ./src/sw.js --bundle --minify --outfile=./dist/sw.js

esbuild will take care of replacing process.env.NODE_ENV with 'development' by default, or 'production' if minification is enabled.

Without a bundler using workbox-sw

Your project may not even use a bundler. workbox-sw can load the Workbox runtime for you from a CDN within your service worker and without a build step if you import it with importScripts:

// sw.js

// Imports Workbox from the CDN. Note that "6.2.0" of the URL
// is the version of the Workbox runtime.

const navigationRoute = new workbox.routing.NavigationRoute(new workbox.strategies.NetworkFirst({
cacheName: 'navigations'

const imageAssetRoute = new workbox.routing.Route(({request}) => {
return request.destination === 'image';
}, new workbox.strategies.CacheFirst({
cacheName: 'image-assets'


Using workbox-sw this way is convenient, but it involves a request to a third-party web server, and will load code that might go unused. Whenever possible, rely on a bundler, as bundlers will drop unused parts of the runtime for better loading performance and avoid potentially costly cross-origin requests.

If the prospect of loading the Workbox runtime from a CDN doesn't seem great, it is possible to use workbox-sw with local URLs.


Now that you know how to use Workbox without precaching, you're no longer tied to a particular bundler or build tool. This gives you the flexibility to handcraft a service worker using just the bits of Workbox's runtime caching code that you're interested in.

Last updated: Improve article

We serve cookies on this site to analyze traffic, remember your preferences, and optimize your experience.