You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Case: I want to define a custom import { Strategy } from "workbox-strategies"; (that fetches data from IndexedDB, so I can use the registerRoute syntax of Workbox).
Will there be any adverse effects if I simply npm i workbox-strategies@6.1.0, along with all the other related packages?
I'll update this issue after I try shortly.
The text was updated successfully, but these errors were encountered:
Use Case: I want to define a custom
import { Strategy } from "workbox-strategies";
(that fetches data from IndexedDB, so I can use theregisterRoute
syntax of Workbox).https://developers.google.com/web/tools/workbox/modules/workbox-strategies#custom_strategies
GoogleChrome/workbox#2455
Strategy.ts
was only introduced in v6.Will there be any adverse effects if I simply
npm i workbox-strategies@6.1.0
, along with all the other related packages?I'll update this issue after I try shortly.
The text was updated successfully, but these errors were encountered: