🎉 What's New?
workbox-webpack-plugin offers more control over paths and filenames
New precacheManifestFilename and importsDirectory options were added to the webpack plugins, giving developers more control over where their generated files are saved.
When importWorkboxFrom: 'local' and output.publicPath is configured, the output.publicPath value will be prepended to the modulePathPrefix used to determine where the Workbox libraries are dynamically loaded from. This amounts to a change in the previous behavior, but based on developer expectation, the previous behavior was considered a bug.
See #1403 for more details about the change, and the documentation for the complete list of configuration options.
New makeRequest() method added to classes under workbox.strategies
Most developers will use one of Workbox's strategies as part of a router configuration. This setup makes it easy to automatically respond to specific fetch events with a response obtained from the strategy.
However, there are situations where making a request using a strategy outside of the standard router setup could be useful. For instance, you might be implementing your own routing logic, or you might want to create a composite response that contains information from multiple smaller responses, stitched together. There are also situations where you'd normally call fetch() directly, but you'd like to take advantage of the plugin integration offered by a strategy class.
See #1408 for more details.
🐛 What's Fixed?
- Use waitUntil only when it's available (#1392) (Thanks to @beatrizdemiguelperez for reporting the underlying issue: #1386)
- Correctly identify when response does not have
dateheader set (#1422) (Thanks to @matthewjmay for identifying the issue and contributing the fix!) - Properly deal with null cachedResponses passed to Range plugin. (#1427)
📖 Learn More
Check out our docs @ developers.google.com/web/tools/workbox/