fix(deps): update workbox monorepo to v6.5.3 #44
Merged
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:
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
6.2.4
->6.5.3
Release Notes
googlechrome/workbox
v6.5.3
Compare Source
v6.5.2
Compare Source
Workbox v6.5.2 includes a number of improvements to the TypeScript documentation and exported types, which should in turn improve the generated documentation.
A full changelog is available at GoogleChrome/workbox@v6.5.1...v6.5.2
v6.5.1
Compare Source
The Workbox v6.5.1 release includes a few changes related to our TypeScript interfaces and documentation.
A full changelog is available at GoogleChrome/workbox@v6.5.0...v6.5.1
What's New
@example
s of using our build tools have been added to the TSDocs forworkbox-build
andworkbox-webpack-plugin
. [#3038]generateSW()
,injectManifest()
, andgetManifest()
methods inworkbox-build
has been updated fromunknown
to an appropriate actual type specific to each method. This should lead to better TSDoc generation and type inferences for developers. As this takes what was previously only a runtime check and moves it to a compile-time check, we believe that it should be functionally equivalent to prior releases, but if you run into problems, please let us know by opening an issue. [#3037]What's Fixed
default
export toworkbox-webpack-plugin
. [#3036]v6.5.0
Compare Source
The Workbox v6.5.0 release includes a number of smaller fixes, as well as a major rewrite of the
workbox-webpack-plugin
to TypeScript.A full changelog is available at GoogleChrome/workbox@v6.4.2...v6.5.0
What's New
workbox-webpack-plugin
has been rewritten in TypeScript, and has public TypeScript definitions for its interfaces published as part of this release. We do not anticipate any changes in the underlying functionality as part of this rewrite. [#2882]forceSyncFallback
parameter has been added toworkbox-background-sync
, without changing the default behavior. WhenforceSyncFallback
is explicitly set totrue
,workbox-background-sync
will always attempt to replay queued requests when the service worker starts up and never rely on thesync
event listener. Most developers will not need this behavior, but it can be useful when targeting environments that have a non-functional Background Sync implementation, like some Electron runtimes. [#3020]What's Fixed
workbox-streams
. [#3001]workbox-background-sync
which could lead to errors when run through with certain aggressive minifiers. [#3012]waitUntil()
was added to theStaleWhileRevalidate
strategy, ensuring that it works properly with navigation preload responses. [#3015]source-map-url
package. [#3031]New Contributors
Thank you to @roikoren755 for their contributions to the
workbox-webpack-plugin
TypeScript migration!v6.4.2
Compare Source
The Workbox v6.4.2 release fixes a few issues:
What's Changed
@apideck/better-ajv-errors
to ^0.3.1 by @wopian in https://github.com/GoogleChrome/workbox/pull/2988ExpirationPlugin
docs by @mungojam in https://github.com/GoogleChrome/workbox/pull/2987workbox wizard --injectManifest
by @jeffposnick in https://github.com/GoogleChrome/workbox/pull/2992New Contributors
Full Changelog: GoogleChrome/workbox@v6.4.1...v6.4.2
v6.4.1
Compare Source
The Workbox v6.4.1 release fixes a few issues:
🐛 What's Fixed?
workbox-build
@apideck/better-ajv-errors
has been updated, which in turn addresses a security issue in one of its dependencies. [#2977]worbox-navigation-preload
preloadResponse
was incorrect, and has been fixed to reflect the previous definition that used to be provided by the TypeScript standard library. [#2975]worbox-strategies
request.url
into account inStrategyHandler.getCacheKey()
. This ensures if a custom strategy overrides theStrategy._handle()
method and performs multiple cache operations on different URLs, the cache key is properly calculated for each distinct URL. [#2973]v6.4.0
Compare Source
Workbox v6.4.0 includes:
🎉 What's New?
worbox-background-sync
size()
. [#2941]🐛 What's Fixed?
injectManifest
. It returns now returns a warning and continues with execution. [#2959]🎁 Thank you
To our new contributors in this version: @StephanBijzitter and @fuzail-ahmed!
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
usespostMessage()
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 configuringBroadcastCacheUpdate
and the associated plugin will result inpostMessage()
only communicating the update to the specificwindow
client that triggered thefetch
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 cachedResponse
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 theconsole
when aResponse
that's being cached includes aVary:
header. [#2916]🐛 What's Fixed?
workbox-cli
chokidar
dependency, for betternode
compatibility and to eliminate security warnings. [#2913]workbox-precaching
PrecacheCacheKeyPlugin
. [#2914]Configuration
📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.