Update dependency workbox-cli to v6.6.0 #81
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.1.5
->6.6.0
Release Notes
googlechrome/workbox (workbox-cli)
v6.6.0
Compare Source
v6.5.4
Compare Source
What's New 👀
config
property [#3056]workbox-precaching
during a fall back to the network, if the request'smode
isno-cors
,integrity
will not be used and the cache entry will not be repaired. [#3099]What's fixed 🐛
Misc 🤹
idb
andselenium-assitant
versionsThank yous 🌿
Full Changelog: GoogleChrome/workbox@v6.5.3...v6.5.4
v6.5.3
Compare Source
v6.5.2
: Workbox v6.5.2Compare 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
: Workbox v6.5.1Compare 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
: Workbox v6.5.0Compare 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
: Workbox v6.4.2Compare 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
: Workbox v6.4.1Compare 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
: Workbox v6.4.0Compare 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
: Workbox v6.3.0Compare 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]v6.2.4
: Workbox v6.2.4Compare Source
🐛 What's Fixed?
onSync
andhandler
ingenerateSW
'sruntimeCaching
should not fail validation. [#2911]v6.2.3
: Workbox v6.2.3Compare Source
🐛 What's Fixed?
@types/trusted-types
todependencies
ofworkbox-window
[#2909]v6.2.2
: Workbox v6.2.2Compare Source
Workbox v6.2.2 fixes a few bugs introduced in the v6.2.0 release.
🐛 What's Fixed?
Validation fix for plugin functions passed to
runtimeCaching
in the build tools. [#2901]Ensure that our
tsc
configuration transpiles newer language features down to the ES2017target
level. [#2902]Update to our
lerna
configuration to use the--exact
tag when publishing tonpm
, to ensure that all the mutual dependencies in the monorepo use exact version matches, and not^
versions. [#2904]v6.2.1
Compare Source
v6.2.0
: Workbox v6.2.0Compare Source
Workbox v6.2.0 includes a number of bug fixes and internal refactoring described below.
Our intention is not to include any breaking changes in v6.2.0, and we've made an effort to maintain the same public interfaces and general behaviors while rewriting some of Workbox's internals.
🎉 What's New?
workbox-build TypeScript rewrite
The
workbox-build
module has been rewritten in TypeScript, following the earlier migration of theworkbox-cli
module. (workbox-webpack-plugin
has not yet been migrated.) Developers who useworkbox-build
from their own TypeScript code should benefit from the official, accurate type definitions that are now published alongsideworkbox-build
. [#2867]Build tool option validation
As part of this change,
workbox-build
now uses the TypeScript definitions as the source of truth when validating the configuration options developers provide. Previously,joi
was used for validation with its own set of schema, and this would sometimes lead to mismatches between what the validation logic thought was okay and what the code actually expected. Developers who inspect the validation errors returned byworkbox-build
will likely see different error strings in v6.2.0. We expect that moving forward, using TypeScript as the source of truth will lead to fewer of those mismatches.This change applies to bothworkbox-cli
andworkbox-webpack-plugin
, as well, which rely onworkbox-build
under the hood.IndexedDB code migration
Another refactoring is the replacement of our previous custom IndexedDB logic with the
idb
library. No developer-visible changes are expected due to this migration. [#2838]Multiple controlling events during a page's lifetime
Following this change,
worbox-window
'scontrolling
event is fired each time the underlyingoncontrollerchange
event happens. Multiplecontrolling
events can occur on a long-lived page in which multiple service worker updates take place.isExternal: true
will be set when the service worker that takes control is "external," which will always be the case for multiple updates.Previously,
controlling
would only be fired once per lifetime of the page, which does not match the documented behavior. This change is considered a bug fix to match the expected behavior, and developers are encouraged to test their logic to ensure that they were not relying on the previous, buggy behavior. [#2817]TrustedScriptURL support in workbox-window
Developers who have opted-in to the CSP policy
"require-trusted-types-for 'script'"
and who are using TypeScript would have previously had trouble usingTrustedScriptURL
s inworkbox-window
. This release improves that support. [#2872]rangeRequests option in runtimeCaching
Setting
rangeRequests: true
inside of aruntimeCaching
configuration entry will add the RangeRequestsPlugin to the service worker generated by Workbox's build tools. [#2871]🐛 What's Fixed?
workbox-core
HandlerDidErrorCallbackParam
type definition is now exported alongside the other relevant TypeScript types. [#2886]workbox-webpack-plugin
webpack
'seval-cheap-source-map
is used along with theInjectManifest
plugin. [#2847]workbox-window
ports
was missing on theWorkboxMessageEvent
. It's been added, mirroring the value of the underlyingMessageEvent
, when used in anonmessage
handler. [#2874]The
WorkboxEventMap
type definition is now exported alongside the other relevant TypeScript types. [#2870]Thanks!
Thank you @rockwalrus for contributing a PR [#2857] that went into this release!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.