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
{{ message }}
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
I know that there's a decent number of folks who follow the issues here, so I wanted to provide a link to some of the team's thinking about the next-generation of service worker libraries: GoogleChrome/workbox#61
We don't have any current plans to end support for sw-toolbox (or sw-precache, for that matter), and we know there are a significant number of web applications that depend on its continued functionality.
But that issue outlines our general thinking about a rearchitecture of the libraries, along with some snippets of code, and is what we expect much of our new development efforts to focus on.
The text was updated successfully, but these errors were encountered:
Would you be open to me adding a short, but consistent message on both sw-precache and sw-toolbox calling out that we're working on the next version of the libraries over in sw-helpers?
Fwiw, React don't currently do this in their main repo for Fiber support (https://github.com/facebook/react/) but given we're moving work to another repo there may be value in doing so.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I know that there's a decent number of folks who follow the issues here, so I wanted to provide a link to some of the team's thinking about the next-generation of service worker libraries: GoogleChrome/workbox#61
We don't have any current plans to end support for
sw-toolbox
(orsw-precache
, for that matter), and we know there are a significant number of web applications that depend on its continued functionality.But that issue outlines our general thinking about a rearchitecture of the libraries, along with some snippets of code, and is what we expect much of our new development efforts to focus on.
The text was updated successfully, but these errors were encountered: