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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Upgrade workbox-routing from 6.0.0-alpha.3 to 6.1.5 #3

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

[Snyk] Upgrade workbox-routing from 6.0.0-alpha.3 to 6.1.5 #3

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade workbox-routing from 6.0.0-alpha.3 to 6.1.5.

merge advice
ℹ️ 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 is 8 versions ahead of your current version.
  • The recommended version was released 3 months ago, on 2021-04-12.
Release notes
Package name: workbox-routing
  • 6.1.5 - 2021-04-12

    Workbox v6.1.5 includes fixes in workbox-cli, workbox-window and workbox-webpack-plugin. Also, the rollup and @ rollup/plugin-node-resolve dependencies were updated.

    (There was no v6.1.3 or v6.1.4 release.)

    🐛 What's Fixed?

    workbox-cli

    In the configuration file generated by workbox wizard the regex for ignoreURLParametersMatching are now serialized correctly, as before they were being serialized as strings and that was causing errors. [#2796]

    workbox-window

    Added support for external controlling events. The controlling event is now dispatched whether it originated in the current or external service worker. Developers can check the isExternal flag to distinguish between the two. [#2786]

    workbox-webpack-plugin

    Fix to push an Error object to compilation.warnings instead of strings, since pushing strings causes the warnings to not be bubbled up correctly. See [#2790]

    Thanks!

    Thank you @ jcabak for contributing documentation updates [#2808]!

  • 6.1.4 - 2021-04-12
  • 6.1.2 - 2021-03-15

    Workbox v6.1.2 includes several fixes to the workbox-cli's wizard mode, and removes some potentially confusing logging.

    🐛 What's Fixed?

    workbox-build

    • A warning message was logged when workbox-build was used, due to an update to the @ rollup/plugin-replace plugin that it uses. The underlying issue raised in the warning message has been addressed. [#2772]

    workbox-cli

    • Previously, the wizard question flow would not give developers the opportunity to specify a value to override the default ignoreURLParametersMatching setting. The wizard now provides some context and explicitly asks about overriding this value. [#2763]

    • There were two issues fixed in the wizard related to entering the globDirectory value: the separator characters, --------, were inadvertently selectable, and additionally, the logic was buggy when a manual directory name was entered. Both of these issues are fixed. [#2766]

    workbox-strategies

    • There was previously unnecessary logging of an uncaught error when a network request failed while offline, even if the response was eventually provided via the cache. This amounted to extra noise in the JS console, and could be particularly confusing if it was triggered during Chrome's new automatic offline check. This uncaught error should no longer show up in the logs. [#2777]

    Thanks!

    Special thanks to @ ognjenjevremovic for contributing the two workbox-cli PRs that went into this release!

  • 6.1.1 - 2021-02-22

    Workbox v6.1.1 includes a bug fix for the NetworkFirst strategy, as well as some documentation and TypeScript fixes.

    🐛 What's Fixed?

    workbox-strategies

    The NetworkFirst strategy uses two promises: one for the network request, and one is the optional networkTimeoutSeconds option is set. If the network request succeeds, then the timeout promise's timer is canceled. However, the strategy previously attempted to wait until both promises resolve before the handler resolves. This meant that, if the network request succeeds before the timeout, the strategy's over handler promise would not properly resolve.

    See #2744

    Thanks!

    Special thanks to @ joshkel for both bringing that NetworkFirst issue to our attention, as well as contributing the code for the fix!

  • 6.1.0 - 2021-01-29

    Workbox v6.1.0 includes a number of new features, as well as an important fix for a bug that could have affected workbox-precaching behavior in earlier v6 releases.

    🎉 What's New?

    setCatchHandler for individual Routes

    The setCatchHandler() method on a Router allows you to configure "fallback" logic if any handler invoked by that Router returns an error. It can be awkward to use, however, if you have many different Routes registered for the same Router, and you would prefer that the fallback logic only be invoked when one or two particular Route handlers fail.

    Starting in this release, each individual Route object has a setCatchHandler() method, allowing you to add fallback logic just to that Route, without affecting any other Routes. To use this method, make sure you explicitly construct a Route first, and then pass that Route to the (overloaded) registerRoute() method:

    Add setCatchHandler option for routes GoogleChrome/workbox#2699

    New "recipes"

    The workbox-recipes module has been extended with a few new features:

    • A new recipe, warmStrategyCache, which takes an array of paths and a Workbox strategy and warms that strategy's cache with those paths at service worker install time.
    • Adds a warmCache option to page, image, and static resource recipes to allow users to warm those caches.
    • Adds a plugins option to page, image, and static resource recipes to allow users to pass additional plugins to those recipes, allowing a user, for instance, to add a URL normalization plugin to the page recipe.

    The workbox-recipes documentation has more information and examples.

    See #2718

    🐛 What's Fixed?

    workbox-precaching

    The expected behavior for workbox-precaching is that all URLs listed in the precache manifest need to be considered "cacheable" in order for service worker installation to succeed. By default, workbox-precaching considers any response with a status code less than 400 as being cacheable (including opaque responses, which have a status code of 0). Developers who need to customize this behavior can pass a cacheWillUpdate plugin to workbox-precaching, and use that logic to determine whether or not a response should be precached during installation.

    Two bugs were introduced in the Workbox v6.0.0 release:

    • The default criteria, in which any response with a status of 400 or higher should be considered uncacheable, would lead to the invalid response being inadvertently written to the cache prior to failing the service worker installation. The next time installation was attempted, this previously cached error response wouldn't be retried, so after enough retries, the service worker would eventually finish installation, even though some responses that should have been considered invalid were precached.

    • If a developer uses a cacheWillUpdate plugin while precaching, returning null from the plugin properly excluded that response from being precached, but it would not cause the overall service worker installation to fail.

    Both of these bugs are fixed in the v6.1.0 release. During service worker installation, if any response that is uncacheable (either via the default or custom cacheWillUpdate criteria) is encountered, installation will consistently fail and the invalid response won't be added to the cache.

    See #2738

    workbox-webpack-plugin

    • Using the chunks or excludeChunks options could lead to a warning message under some circumstances, due to workbox-webpack-plugin assuming they always corresponded to chunk group names. The code will now check to see if the name matches a chunk itself, not just a group. See #2735

    All build tools

    • The source-map dependency has been updated to resolve an issue that could occur when run in a Node environment that had a polyfilled fetch(). See #2716

    Thanks!

    Special thanks to @ Spiderpig86 for contributing a PR that was part of this release.

  • 6.0.2 - 2020-12-03

    Workbox v6.0.2 resolves an issue that could prevent workbox-precaching from working as expected when loaded via workbox-sw.

    (There was no v6.0.1 release.)

    🐛 What's Fixed?

    • Preserve symbols across builds and don't mangle _handle. [#2687]

    Thanks!

    Special thanks to @ pidtuner for raising the issue that was resolved in this release.

  • 6.0.0 - 2020-11-30
    Read more
  • 6.0.0-rc.0 - 2020-11-16

    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 requires webpack v4.40.0 or later (for those still on the v4.x branch) or webpack v.5.4.0 or later (for those who have updated to webpack v5.x).

    workbox-webpack-plugin will also now take advantage of the immutable metadata that webpack automatically adds to hashed assets. In most cases, this means that explicitly using dontCacheBustURLMatching in your workbox-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 in npm for the current pre-release version. To install a given module use, e.g., npm install --save-dev workbox-webpack-plugin@next.

  • 6.0.0-alpha.3 - 2020-10-12
    Read more
from workbox-routing GitHub release notes
Commit messages
Package name: workbox-routing

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

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@snyk-bot