Describe the reason for these changes and the problem that they solve
It looks like the Workbox library that we've been using to help build our application may no longer be maintained.
The interface and functionality Workbox provides have been stable, so there's been no urgent reason for us to look for alternatives, but it does have some static dependencies on other libraries where vulnerabilities are being uncovered, and although if we had complete confidence that we're not affected by those, then we could leave Workbox as a dependency, it's difficult to build that level of assurance.
As visible from the diff here, we're able to drop a good number of dependencies by doing this, and smaller surface area should generally infer longer-term safety when functionality is stable (fewer moving parts, more focus from developers, more likely to be adopted by other consumers thanks to improved auditability, ...).
Describe the reason for these changes and the problem that they solve
It looks like the Workbox library that we've been using to help build our application may no longer be maintained.
The interface and functionality Workbox provides have been stable, so there's been no urgent reason for us to look for alternatives, but it does have some static dependencies on other libraries where vulnerabilities are being uncovered, and although if we had complete confidence that we're not affected by those, then we could leave Workbox as a dependency, it's difficult to build that level of assurance.
As visible from the diff here, we're able to drop a good number of dependencies by doing this, and smaller surface area should generally infer longer-term safety when functionality is stable (fewer moving parts, more focus from developers, more likely to be adopted by other consumers thanks to improved auditability, ...).
Briefly summarize the changes
workbox-*to the equivalent@serwist/*dependencies.How have the changes been tested?
List any issues that this change relates to N/A