chore(deps): update dependency workbox-build to v3.6.3 #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.4.1
->3.6.3
Release Notes
googlechrome/workbox
v3.6.3
Compare Source
🐛 What's Fixed?
This release fixes an issue (#1677) that several users have reported, triggered by precaching a URL that returns a 30x redirect to another URL. For instance, having
'/index.html'
listed in your precache manifest can trigger this issue, if your web server responds to requests for'/index.html
' with a 301 redirect to the destination URL'/'
. When the issue manifests itself, the final, redirect content ends up being served with an incorrectContent-Type:
response header, which can in turn lead problems displaying that cached content.If you do use 30x redirects for some of your URLs, we recommend updating to this latest release of Workbox.
In order to "clear out" the problematic content that was previously precached with an incorrect
Content-Type
, after updating Workbox, you can deploy a small change to URLs that you know are affected (i.e. make any change to your'/index.html
' file, if that's being fulfilled with a 30x redirect).It's also possible to force all previously cached entries to be precached again by changing the
cacheId
option in "generate SW" mode, or by includingin your service worker source file in "inject manifest" mode.
📖 Learn More
Check out our docs @ developers.google.com/web/tools/workbox/
v3.6.2
Compare Source
🎉 What's New?
This release contains a fix for a missing
dependency
entry inworkbox-webpack-plugin
'spackage.json
. Thanks to @arcanis for contributing the fix in #1667!There are no functional changes in this release.
📖 Learn More
Check out our docs @ developers.google.com/web/tools/workbox/
v3.6.1
Compare Source
🎉 What's New?
Added the
disable()
method toworkbox.navigationPreload
workbox.navigationPreload
provides anenable()
method to enable navigation preload, but it did not provide a way to disable it (without invoking the underlying service worker APIs). Now developers can callworkbox.navigationPreload.disable()
to disable navigation preload. (#1651)The
method
option can now be used for runtime caching viagenerateSW()
method
option from being used by runtime caching configuration ingenerateSW()
. Thanks to @chrisdns, this has been fixed! (#1638)Bug fixes and ergonomic improvements
workbox.expiration.Plugin
withpurgeOnQuotaError
set totrue
would result in an error. Thanks to @salmoro for discovering and fixing the issue! (#1643).event
that triggered them, so developers writing custom plugins could not access any information about the event in those callback. Now all plugin callback are passed the event object (when available). (#1640)workbox-streams
package'sstrategy()
method is exposed on the browser build ofworkbox.streams
that gets loaded by theworkbox-sw
loader, but it wasn't exported by the module in a way that was accessible to module bundlers. Now it's possible to import{strategy}
fromworkbox-streams/strategy.mjs
. (#1635).📖 Learn More
Check out our docs @ developers.google.com/web/tools/workbox/
v3.5.0
Compare Source
🎉 What's New?
More customization when generating a service worker
Developers who use Workbox to generate their service worker (using the CLI, Node interface, or webpack plugin) can now take advantage of some additional options:
Setting
offlineGoogleAnalytics: true
will automatically add code to initialize Workbox's offline Google Analytics support in the generated service worker.Both
fetchOptions
andmatchOptions
can now be used when configuring aruntimeCaching
route, and those values will be passed through when constructing the corresponding Workbox caching strategy. Many thanks to @peterjosling for contributing this in #1608.Using a custom plugin within a
runtimeCaching
route is now possible, thanks to enhancements made by @tsirlucas in #1598.Here's a snippet of Workbox's build configuration, showing off all of the new features:
Support for the
PATCH
method in Workbox's routerDevelopers who need to match HTTP
PATCH
requests using Workbox's router can now do so, thanks to @kevin-brotcke's change in #1618.Note that non-
GET
requests can't be added to a cache, so this is most useful when used alongside a network-only strategy configured with the Workbox background sync plugin, in order to retry failedPATCH
requests once the network becomes available.workbox.core.registerQuotaErrorCallback
is now publicly visibleDue to a scoping error, the
workbox.core.registerQuotaErrorCallback()
function was previously not exposed. This is now public, matching the documented interface. Thanks to @Tronil for pointing out this discrepancy in #1616.📖 Learn More
Check out our docs @ developers.google.com/web/tools/workbox/
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!
".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.