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
Back when I was first involved in the c-r-a project, there was no flexibility to install additional packages beyond what was provided by the official configuration. I believe that this restriction still applies, or at least it's not very straightforward to add in packages beyond what's in the template's configuration.
The thinking here was that if somewhere were to read through the https://developer.chrome.com/docs/workbox/ documentation and realize that they needed to modify their service worker to use a module like workbox-google-analytics, they would be unable to add it in after the fact—and there wouldn't be a clear way to explain in the Workbox docs which modules are included with c-r-a and which aren't.
Maybe things have changed in the c-r-a ecosystem since the earlier days, and it's now easier to add in additional packages after setting things up from a template? I'm not very active in the c-r-a ecosystem right now, so I am not sure. If someone can confirm that c-r-a is now flexible enough to do that, we can drop all of the packages that aren't used directly by the default service worker's code.
Why do you need all these dependencies
![image](https://user-images.githubusercontent.com/42112796/97614898-36c52780-1a23-11eb-97f0-2981ef098273.png)
For example I don't see any use of
workbox-google-analytics
in this templateThe text was updated successfully, but these errors were encountered: