From 3da39e28b44cc2611b00cfc9a1e38004c626db8f Mon Sep 17 00:00:00 2001 From: Ayo Ayco Date: Thu, 8 Aug 2024 21:36:01 +0200 Subject: [PATCH] chore: update readme --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 245cd15..da4985f 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,10 @@ -> **>>> TL;DR:** Simple Astro integration to use your own authored service worker; by default, devs retain full control as opposed to getting generated sw code - # Astro SW [![Package information: NPM version](https://img.shields.io/npm/v/@ayco/astro-sw)](https://www.npmjs.com/package/@ayco/astro-sw) [![Package information: NPM license](https://img.shields.io/npm/l/@ayco/astro-sw)](https://www.npmjs.com/package/@ayco/astro-sw) [![Bundle Size](https://img.shields.io/bundlephobia/minzip/@ayco/astro-sw)](#library-size) -The integration accepts service worker path and automatically injects dynamic variables such as `__assets` generated by Astro for caching. - -The main philosophy is to [invert the control](https://en.wikipedia.org/wiki/Inversion_of_control) compared to other integrations that generate the service worker for devs. The [service worker](https://web.dev/articles/offline-cookbook) API is such a powerful feature that developers need to be able to make decisions in using it. +The integration accepts path to your own authored [service worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) and automatically injects dynamic variables such as `__assets` generated by Astro for caching. The goal is to [invert the control](https://en.wikipedia.org/wiki/Inversion_of_control) (i.e., compared to generating the service worker script code), and let devs retain the flexibility for various [caching strategies](https://developer.chrome.com/docs/workbox/caching-strategies-overview/). ## Installation