dependabot-preview[bot]
commented
5 years ago OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
Updates the requirements on workbox-webpack-plugin to permit the latest version.
Release notes
*Sourced from [workbox-webpack-plugin's releases](https://github.com/googlechrome/workbox/releases).* > ## Workbox v4.0.0 > # Overview of Workbox v4 > > We're happy to announce the release of Workbox version 4! This release introduces a lot of great new features, as well as some breaking changes. > > You can read the full list of changes here; we've also published a guide on [migrating from v3 to v4](https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-v3). > > ## š What's New? > > ### `workbox-window` > > The `workbox-window` package is a set of modules that are intended to run in the [window context](https://developer.mozilla.org/en-US/docs/Web/API/Window), which is to say, inside of your web pages. They're a complement to the other workbox packages that run in the service worker. > > The key features/goals of `workbox-window` are: > > * To simplify the process of service worker registration and updates by helping developers identify the [most critical moments in the service worker lifecycle](https://developers.google.com/web/tools/workbox/modules/workbox-window#important-service-worker-lifecycle-moments), and making it easier to respond to those moments. > * To help prevent developers from making the [most common mistakes](https://developers.google.com/web/tools/workbox/modules/workbox-window#avoiding-common-mistakes). > * To enable [easier communication](https://developers.google.com/web/tools/workbox/modules/workbox-window#window-to-service-worker-communication) between code running in the service worker and code running in the window. > > You can use `workbox-window` by importing it into your code from our CDN as show in the following example: > > ```html > > ``` > > To learn more, see the [`workbox-window` usage guide](https://developers.google.com/web/tools/workbox/modules/workbox-window) or the [`Workbox` class reference documentation](https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-window.Workbox). > > ### `workbox-routing` > > - Logging has improved for `workbox.routing.NavigationRoute` when a URL matches the blacklist. Now a message with higher priority is logged when using the development builds. [#1741] > > - `workbox.routing.Router` now includes a `routes` getter method, giving developers access to the underlying `Map` of routes that have been registered for a given router. [#1714] > > - The `Router#handleRequest()` method no longer requires an `event` be passed, which allows routing logic to be used programmatically, outside of the context of a `fetch` event. This can be useful as a way to cache URLs using the same strategies and plugins that you've already defined in your routing logic. [#1682] > > ### `workbox-google-analytics` > > - If you use Google Tag Manager (GTM) to load Google Analytics on your site, Workbox will now cache the `gtm.js` library so it will work offline as well [#1869]. > > ### `workbox-broadcast-update` > > - The `workbox-broadcast-update` plugin now works in browsers that don't support the `BroadcastChannel` API by iterating over all the open [window clients](https://developer.mozilla.org/en-US/docs/Web/API/WindowClient) and sending them the update message via [`postMessage()` API](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage). In addition, the `channel` parameter is no longer required. If no channel is given the default channel name `workbox` is used (no channle is used for browsers that don't support the `BroadcastChannel` API). [#1673] > ... (truncated)Commits
- [`51ec243`](https://github.com/GoogleChrome/workbox/commit/51ec243c7afc67d5cec835b685bd9ad1e70fb78b) v4.0.0 - [`07d7cb6`](https://github.com/GoogleChrome/workbox/commit/07d7cb6fa484e8437243ce149eb14e64f0c2ba5e) Remove npm beta tag ([#1918](https://github-redirect.dependabot.com/googlechrome/workbox/issues/1918)) - [`5081164`](https://github.com/GoogleChrome/workbox/commit/5081164dce94a4d24faa876778aa6b2170ad32fd) Update version metadata ([#1917](https://github-redirect.dependabot.com/googlechrome/workbox/issues/1917)) - [`cddab54`](https://github.com/GoogleChrome/workbox/commit/cddab54b7b1b7fee18765dcf8350f7e118285efb) v4.0.0-rc.4 - [`76f3e0f`](https://github.com/GoogleChrome/workbox/commit/76f3e0fcb8a0c49a908f5566f6f597dcb480b0ac) Merge pull request [#1914](https://github-redirect.dependabot.com/googlechrome/workbox/issues/1914) from GoogleChrome/bcu-precaching - [`c5ceb9b`](https://github.com/GoogleChrome/workbox/commit/c5ceb9b08c625e40fd8e43d2bf0a105ab9ebcb46) Use ignoreSearch to fix precaching broadcast updates. - [`0d528c9`](https://github.com/GoogleChrome/workbox/commit/0d528c947f027d2e1ae57a9c4c5a566388503ba8) Add a null check for cache listener message data ([#1913](https://github-redirect.dependabot.com/googlechrome/workbox/issues/1913)) - [`2d8ce9a`](https://github.com/GoogleChrome/workbox/commit/2d8ce9ac380b8d3cfa63a5e12f544e458d36dfe9) Merge pull request [#1912](https://github-redirect.dependabot.com/googlechrome/workbox/issues/1912) from GoogleChrome/cache-listener-events - [`47157a7`](https://github.com/GoogleChrome/workbox/commit/47157a70db888243d3a116c71790eb3bed34717e) Update cache message wait until logic - [`196f9b3`](https://github.com/GoogleChrome/workbox/commit/196f9b37ff2dc78f19447aaa339338774261905e) Update log messages on redundant SW ([#1910](https://github-redirect.dependabot.com/googlechrome/workbox/issues/1910)) - Additional commits viewable in [compare view](https://github.com/googlechrome/workbox/compare/v3.0.1...v4.0.0)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.