9 | An Astro integration that generates a Service Worker. Powered by Workbox.4 | 5 |
9 |
10 |
11 | 
12 |
13 |
14 | 
15 |
16 |
17 | 
18 |
19 |
20 | 
21 |
22 |
23 | 
24 |
25 |
26 | ## What is this? 🧐
27 |
28 | A minimal wrapper around [Workbox](https://developers.google.com/web/tools/workbox) to quickly add a [service worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) to your [Astro](https://astro.build/) static site. Get precached pages and offline support out of the box.
29 |
30 | ## Installation & Usage 📦
31 |
32 | 1. Add this package to your project:
33 | - `npm install astrojs-service-worker` or `yarn add astrojs-service-worker`
34 | 2. Add `astrojs-service-worker` to your [astro.config.mjs](https://docs.astro.build/en/reference/configuration-reference/) integrations:
35 |
36 | ```diff
37 | import { defineConfig } from "astro/config";
38 | + import serviceWorker from "astrojs-service-worker";
39 |
40 | export default defineConfig({
41 | + integrations: [serviceWorker()],
42 | });
43 | ```
44 |
45 | 3. That's it! A service worker that precaches all of your build's static assets will be generated. Page navigations will be served from the service worker's cache instead of making network calls, speeding up your page views and enabling offline viewing 🙌.
46 |
47 | _Note that when running `astro dev` a no-op service worker is generated. Service workers interfere with hot module reloading (because they intercept the request for the updated asset), so this no-op service worker clears any existing workers for the page so hot module reloading works as expected._
48 |
49 | ## Verification 🤔
50 |
51 | 1. To view the production service worker, run `astro build && astro preview`.
52 | 2. The service worker must first install before it intercepts any traffic. You can view the status of the service worker in Chrome by opening the dev console, clicking the `Application` tab and then clicking the `Service Workers` tab.
53 | 3. Disable your internet connection and click around your site. Your pages will be served by the service worker. This is most obvious when you are disconnected from the internet, but even when users have an internet connection your pages will be served from the service worker and not from the network -- markedly speeding up page requests.
54 |
55 | ## API Overview 🛠
56 |
57 | | Name | 61 |Description | 62 |Type | 63 |
|---|---|---|
| registration.autoRegister | 69 |70 | 71 | Autoregister the service worker. 72 | 73 | If `false`, then the application must initialize the service worker by invoking `register`. Set this to `false` if you'd like to take control over when you service worker is initialized. You'll then need to add something like the following to your application: 74 | 75 | ```javascript 76 | if ("serviceWorker" in navigator) { 77 | navigator.serviceWorker.register("/service-worker.js"); 78 | } 79 | ``` 80 | 81 | Defaults to `true`. Recommended: `true`. 82 | 83 | | 84 | 85 |boolean | undefined | 86 |
| workbox | 90 |91 | Options passed to `worbox-build`. See all available configuration options [here](https://developer.chrome.com/docs/workbox/modules/workbox-build/) 92 | 93 | Defaults to `GenerateSW` which will generate a service worker. 94 | 95 | Note: `injectManifest` is not supported at this time. If you would like it to be supported, please [open an issue](https://github.com/tatethurston/astrojs-service-worker/issues/new") 96 | 97 | | 98 |InjectManifestOptions | GenerateSWOptions | 99 |
16 |