[Snyk] Upgrade workbox-build from 6.0.0-alpha.1 to 6.0.0 #2
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.
Snyk has created this PR to upgrade workbox-build from 6.0.0-alpha.1 to 6.0.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version fixes:
SNYK-JS-SERIALIZEJAVASCRIPT-570062
Why? Proof of Concept exploit, Has a fix available, CVSS 7.7
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: workbox-build
Read more
Overview of Workbox v6
We're happy to announce the first release candidate of Workbox v6! We do not anticipate any more breaking changes in between now and the official v6 release.
In addition to the changes outlined in the previous release notes, the following has changed since Workbox v5.
🎉 What's New?
workbox-recipes
This release includes a new module,
workbox-recipes
, that combines common routing and caching strategy configurations into ready-to-use code that can be dropped in to your service worker.You can read more about what's included in the first batch of recipes, as well as how to use them, in #2664.
webpack v5 compatibility improvements
This release includes additional bug fixes for better compatibility with
webpack
. As of this release,workbox-webpack-plugin
requireswebpack
v4.40.0 or later (for those still on the v4.x branch) orwebpack
v.5.4.0 or later (for those who have updated towebpack
v5.x).workbox-webpack-plugin
will also now take advantage of theimmutable
metadata thatwebpack
automatically adds to hashed assets. In most cases, this means that explicitly usingdontCacheBustURLMatching
in yourworkbox-webpack-plugin
configuration is no longer necessary.See #2651, #2673, and #2675.
Thanks!
Thank you to @ dermoumi for their contributions to this release.
Installation of the latest pre-release version
We are using the
next
tag innpm
for the current pre-release version. To install a given module use, e.g.,npm install --save-dev workbox-webpack-plugin@next
.Overview of Workbox v6
We're happy to announce the third alpha release of Workbox v6! In addition to the changes outlined in the previous release notes, the following has changed since Workbox v5.
🎉 What's New?
Under-the-hood workbox-precaching improvements
This release includes a substantial rewrite to the implementation of
workbox-precaching
, to build on top of other standard Workbox idioms (likeRoute
s,Strategy
subclasses, and custom plugins) as much as possible. There are a few breaking changes, described in the follow section, but they are mostly limited to uncommon use cases, whenPrecacheController
is instantiated directly. For the most part, these changes are meant to be invisible to developers, but should lead to be better consistency in how routing and request handling works across all of Workbox.You can read more about what's change in #2638
webpack v5 compatibility
As of this release,
workbox-webpack-plugin
should be compatible withwebpack
v5.0.0. We have also raised the minimum required version ofwebpack
to v4.4.0, which should be a straightforward upgrade for developers who need to remain onwebpack
v4.x.While all of the public interfaces remain the same, signfifcant changes were made to the code used to determine which
webpack
assets make it into your precache manifest. These take advantage of new methods that were added inwebpack
v4.4.0, and which have to be used inwebpack
v5.0.0. We encourage developers to testworkbox-webpack-plugin
carefully, and raise issues if you find discrepencies like URLs missing from your precache manifest! This applies whether you are remaining onwebpack
v4.4.0, or are upgrade towebpack
v5.0.0.Note: At this time,
workbox-webpack-plugin
has issues detecting the correct URLs for HTML assets created byhtml-webpack-plugin
inwebpack
v5.0.0. You can follow jantimon/html-webpack-plugin#1522 for updates.cacheKeyWillBeUsed can be used to cache non-GET requests
Only
GET
requests can be used as cache keys, but there are scenarios in which you might want to use a combination of plugins to transform aPOST
orPUT
request into a cacheableGET
request.You can now use the
cacheKeyWillBeUsed
lifecycle callback in a plugin to return aGET
request with whatever URL you'd like to use as a cache key, and that can then allow the response associated with aPOST
orPUT
to be cached.See #2615 for more details. Thanks to @ markbrocato for their contribution.
workbox-precaching
Note: The following changes primarily apply to direct usage of the
PrecacheController
class. Most developers don't usePrecacheController
directly, and instead use static helper methods likeprecacheAndRoute()
exported byworkbox-precaching
. [#2639]The
PrecacheController
constructor now takes in an object with specific properties as its parameter, instead of a string. This object supports the following properties:cacheName
(serving the same purpose as the string that was passed in to the constructor in v5),plugins
(replacing theaddPlugins()
method from v5), andfallbackToNetwork
(replacing the similar option that was passed tocreateHandler()
and `createHandlerBoundToURL() in v5).The
install()
andactivate()
methods ofPrecacheController
now take exactly one parameter, which should be set to a correspondingInstallEvent
orActivateEvent
, respectively.The
addRoute()
method has been removed fromPrecacheController
. In its place, the newPrecacheRoute
class can be used to create a route that you can then register.The
precacheAndRoute()
method has been removed fromPrecacheController
. (It still exists as a static helper method exported by theworkbox-precaching
module.) It was removed becausePrecacheRoute
can be used instead.The
createMatchCalback()
method has been removed fromPrecacheController
. The newPrecacheRoute
can be used instead.The
createHandler()
method has been removed fromPrecacheController
. Thestrategy
property of thePrecacheController
object can be used to handle requests instead.The
createHandler()
static export has already been removed from theworkbox-precaching
module. In its place, developers should construct aPrecacheController
instance and use itsstrategy
property.The route registered with
precacheAndRoute()
is now a "real" route that usesworkbox-routing
'sRouter
class under the hood. This may lead to a different evaluation order of your routes if you interleave calls toregisterRoute()
andprecacheAndRoute()
. See #1857 and #2402 for more details.workbox-webpack-plugin
v4.4.0
. (See previous section for otherwebpack
updates.) [#2641]Installation of the latest pre-release version
We are using the
next
tag innpm
for the current pre-release version. To install a given module use, e.g.,npm install --save-dev workbox-webpack-plugin@next
.Workbox
v6.0.0-alpha.2
includes updates to various underlyingnpm
dependencies, but is otherwise identical to the previousv6.0.0-alpha.1
release.Installation of the latest pre-release version
We are using the
next
tag innpm
for the current pre-release version. To install a given module use, e.g.,npm install --save-dev workbox-webpack-plugin@next
.Read more
Commit messages
Package name: workbox-build
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
👩💻 Set who automatically gets assigned
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs