Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency workbox-webpack-plugin to v6.6.0 #518

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 5, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
workbox-webpack-plugin (source) 6.1.5 -> 6.6.0 age adoption passing confidence

Release Notes

googlechrome/workbox (workbox-webpack-plugin)

v6.6.0

Compare Source

v6.5.4

Compare Source

What's New 👀

  • Webpack plugin can be extended and subclasses can access the config property [#​3056]
  • In workbox-precaching during a fall back to the network, if the request's mode is no-cors, integrity will not be used and the cache entry will not be repaired. [#​3099]

What's fixed 🐛

Misc 🤹

  • updated idb and selenium-assitant versions

Thank yous 🌿

Full Changelog: GoogleChrome/workbox@v6.5.3...v6.5.4

v6.5.3

Compare Source

v6.5.2: Workbox 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: Workbox 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

  • Additional inline @examples of using our build tools have been added to the TSDocs for workbox-build and workbox-webpack-plugin. [#​3038]
  • The TypeScript type for the generateSW(), injectManifest(), and getManifest() methods in workbox-build has been updated from unknown 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

  • We have re-added the default export to workbox-webpack-plugin. [#​3036]

v6.5.0: Workbox 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]
  • A forceSyncFallback parameter has been added to workbox-background-sync, without changing the default behavior. When forceSyncFallback is explicitly set to true, workbox-background-sync will always attempt to replay queued requests when the service worker starts up and never rely on the sync 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

  • A more informative message is returned when an opaque response is erroneously used in workbox-streams. [#​3001]
  • Removed a dynamic method call in workbox-background-sync which could lead to errors when run through with certain aggressive minifiers. [#​3012]
  • A waitUntil() was added to the StaleWhileRevalidate strategy, ensuring that it works properly with navigation preload responses. [#​3015]
  • Removed the dependency on the deprecated 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.2

Compare Source

The Workbox v6.4.2 release fixes a few issues:

What's Changed

New Contributors

Full Changelog: GoogleChrome/workbox@v6.4.1...v6.4.2

v6.4.1: Workbox v6.4.1

Compare Source

The Workbox v6.4.1 release fixes a few issues:

🐛 What's Fixed?

workbox-build
worbox-navigation-preload
  • The inline TypeScript definition for 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
  • Take request.url into account in StrategyHandler.getCacheKey(). This ensures if a custom strategy overrides the Strategy._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.0

Compare Source

Workbox v6.4.0 includes:

🎉 What's New?

  • We upgraded to TypeScript 4.4.3. This required us to declare inline some types that are now longer part of the TypeScript standard; see #​2946 for more context. [#​2950]
worbox-background-sync
  • You can check the number of requests in the sync queue with the new method size(). [#​2941]

🐛 What's Fixed?

  • We upgraded @​surma/rollup-plugin-off-main to patch a vulnerability from the dependency. [#​2962]
  • A missing sourcemap is no longer a fatal error when running 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.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]

v6.2.4: Workbox v6.2.4

Compare Source

🐛 What's Fixed?
  • Passing in functions for onSync and handler in generateSW's runtimeCaching should not fail validation. [#​2911]

v6.2.3: Workbox v6.2.3

Compare Source

🐛 What's Fixed?
  • Move @types/trusted-types to dependencies of workbox-window [#​2909]

v6.2.2: Workbox v6.2.2

Compare 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 ES2017 target level. [#​2902]

  • Update to our lerna configuration to use the --exact tag when publishing to npm, 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.0

Compare 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 the workbox-cli module. (workbox-webpack-plugin has not yet been migrated.) Developers who use workbox-build from their own TypeScript code should benefit from the official, accurate type definitions that are now published alongside workbox-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 by workbox-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 both workbox-cli and workbox-webpack-plugin, as well, which rely on workbox-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's controlling event is fired each time the underlying oncontrollerchange event happens. Multiple controlling 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 using TrustedScriptURLs in workbox-window. This release improves that support. [#​2872]

rangeRequests option in runtimeCaching

Setting rangeRequests: true inside of a runtimeCaching configuration entry will add the RangeRequestsPlugin to the service worker generated by Workbox's build tools. [#​2871]

🐛 What's Fixed?

workbox-core
  • The HandlerDidErrorCallbackParam type definition is now exported alongside the other relevant TypeScript types. [#​2886]
workbox-webpack-plugin
  • A bug was fixed that could lead to invalid generated code when quotation chars when webpack's eval-cheap-source-map is used along with the InjectManifest plugin. [#​2847]
workbox-window
  • ports was missing on the WorkboxMessageEvent. It's been added, mirroring the value of the underlying MessageEvent, when used in an onmessage 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 - "after 5am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from 1def96c to 2370b3e Compare August 6, 2021 20:21
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.2.0 Update dependency workbox-webpack-plugin to v6.2.2 Aug 6, 2021
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from 2370b3e to 848b13f Compare August 10, 2021 17:39
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.2.2 Update dependency workbox-webpack-plugin to v6.2.3 Aug 10, 2021
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from 848b13f to 71a4c06 Compare August 11, 2021 18:58
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.2.3 Update dependency workbox-webpack-plugin to v6.2.4 Aug 11, 2021
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from 71a4c06 to ebe02c5 Compare October 18, 2021 16:28
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.2.4 Update dependency workbox-webpack-plugin to v6.3.0 Oct 18, 2021
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from ebe02c5 to f49dc45 Compare March 7, 2022 14:10
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.3.0 Update dependency workbox-webpack-plugin to v6.5.1 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from f49dc45 to 44dd8c2 Compare March 26, 2022 12:33
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.5.1 Update dependency workbox-webpack-plugin to v6.5.2 Mar 26, 2022
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from 44dd8c2 to d94c937 Compare April 24, 2022 23:00
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.5.2 Update dependency workbox-webpack-plugin to v6.5.3 Apr 24, 2022
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from d94c937 to c1d8a3c Compare September 25, 2022 16:28
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.5.3 Update dependency workbox-webpack-plugin to v6.5.4 Sep 25, 2022
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.5.4 Update dependency workbox-webpack-plugin to v6.6.0 May 28, 2023
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch 2 times, most recently from e7f62c8 to 51fbc81 Compare May 30, 2023 21:38
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.6.0 Update dependency workbox-webpack-plugin to v6.6.1 May 30, 2023
@renovate renovate bot changed the title Update dependency workbox-webpack-plugin to v6.6.1 Update dependency workbox-webpack-plugin to v6.6.0 May 31, 2023
@renovate renovate bot force-pushed the renovate/workbox-webpack-plugin-6.x branch from 51fbc81 to 04ed712 Compare May 31, 2023 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants