chore(deps): update workbox monorepo to v6.3.0 #730

renovate · 2021-09-09T18:01:36Z

renovate commented

2021-09-09 18:01:36 +00:00

This PR contains the following updates:

Package	Type	Update	Change
workbox-cli	devDependencies	minor	`6.2.4` -> `6.3.0`
workbox-precaching	dependencies	minor	`6.2.4` -> `6.3.0`

Release Notes

googlechrome/workbox

`v6.3.0`

Compare Source

Workbox v6.3.0 includes a couple of bug fixes and several new features.

🎉 What's New?

Allow precaching "repair" when using subresource integrity

Although unexpected, there are edge cases where the precache might not be in an inconsistent state, most likely due to a developer manually deleting something in DevTools.

When this happens, workbox-precaching defaults to falling-back to using a network response (assuming the device is online) when there's a precaching miss. Up until now, workbox-precaching hasn't attempting to use this network response to repopulate the precache, because there are no guarantees that the network response corresponds to the version of the asset specified in the precache manifest.

However, if the precache entry includes an integrity property, then subresource integrity guarantees that the response does correspond to the same version of the asset in the manifest. So it should be safe to "repair" the cache with that response. [#2921]

IDB writes use relaxed durability

This small change to the way Workbox writes to IndexedDB should lead to slightly better performance, without any appreciable downsides. [#2934]

notifyAllClients option in BroadcastCacheUpdate

BroadcastCacheUpdate uses postMessage() to notify all open tabs controlled by the current service worker about a cache update. This default behavior is not changing.

Setting notifyAllClients: false when configuring BroadcastCacheUpdate and the associated plugin will result in postMessage() only communicating the update to the specific window client that triggered the fetch request which resulted in the cache update. [#2920]

All WorkboxEvents TypeScript types are now exported

This enhancement makes it easier to use TypeScript to write workbox-window event handlers. [#2919]

Debug logging when caching responses with Vary: headers

The presence of Vary: headers on a cached Response can make it difficult to properly match and delete cache entries. To make it clearer to developers when this is happening, the development builds of Workbox will now log a message to the console when a Response that's being cached includes a Vary: header. [#2916]

🐛 What's Fixed?

workbox-cli

Update to chokidar dependency, for better node compatibility and to eliminate security warnings. [#2913]

workbox-precaching

Preserve all request headers in PrecacheCacheKeyPlugin. [#2914]

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 you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [workbox-cli](https://github.com/googlechrome/workbox) | devDependencies | minor | [`6.2.4` -> `6.3.0`](https://renovatebot.com/diffs/npm/workbox-cli/6.2.4/6.3.0) | | [workbox-precaching](https://github.com/googlechrome/workbox) | dependencies | minor | [`6.2.4` -> `6.3.0`](https://renovatebot.com/diffs/npm/workbox-precaching/6.2.4/6.3.0) | --- ### Release Notes <details> <summary>googlechrome/workbox</summary> ### [`v6.3.0`](https://github.com/googlechrome/workbox/releases/v6.3.0) [Compare Source](https://github.com/googlechrome/workbox/compare/v6.2.4...v6.3.0) Workbox v6.3.0 includes a couple of bug fixes and several new features. ##### 🎉 What's New? ##### Allow precaching "repair" when using subresource integrity Although unexpected, there are edge cases where the precache might not be in an inconsistent state, most likely due to a developer manually deleting something in DevTools. When this happens, `workbox-precaching` defaults to falling-back to using a network response (assuming the device is online) when there's a precaching miss. Up until now, `workbox-precaching` hasn't attempting to use this network response to repopulate the precache, because there are no guarantees that the network response corresponds to the version of the asset specified in the precache manifest. However, if the precache entry includes an [`integrity` property](https://developers.google.com/web/tools/workbox/modules/workbox-precaching#using_subresource_integrity), then [subresource integrity](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) guarantees that the response *does* correspond to the same version of the asset in the manifest. So it should be safe to "repair" the cache with that response. \[[#2921](https://github.com/googlechrome/workbox/issues/2921)] ##### IDB writes use relaxed durability This small change to the way Workbox writes to IndexedDB should lead to slightly better performance, without any appreciable downsides. \[[#2934](https://github.com/googlechrome/workbox/issues/2934)] ##### notifyAllClients option in BroadcastCacheUpdate `BroadcastCacheUpdate` uses `postMessage()` to notify all open tabs controlled by the current service worker about a cache update. This default behavior is not changing. Setting `notifyAllClients: false` when configuring `BroadcastCacheUpdate` and the associated plugin will result in `postMessage()` only communicating the update to the specific `window` client that triggered the `fetch` request which resulted in the cache update. \[[#2920](https://github.com/googlechrome/workbox/issues/2920)] ##### All WorkboxEvents TypeScript types are now exported This enhancement makes it easier to use TypeScript to write `workbox-window` event handlers. \[[#2919](https://github.com/googlechrome/workbox/issues/2919)] ##### Debug logging when caching responses with Vary: headers The presence of `Vary:` headers on a cached `Response` can make it difficult to properly match and delete cache entries. To make it clearer to developers when this is happening, the development builds of Workbox will now log a message to the `console` when a `Response` that's being cached includes a `Vary:` header. \[[#2916](https://github.com/googlechrome/workbox/issues/2916)] ##### 🐛 What's Fixed? ##### workbox-cli - Update to `chokidar` dependency, for better `node` compatibility and to eliminate security warnings. \[[#2913](https://github.com/googlechrome/workbox/issues/2913)] ##### workbox-precaching - Preserve all request headers in `PrecacheCacheKeyPlugin`. \[[#2914](https://github.com/googlechrome/workbox/issues/2914)] </details> --- ### 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 you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate added the

dependencies

label 2021-09-09 18:01:36 +00:00

renovate added 1 commit 2021-09-09 18:01:36 +00:00