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-build from 4.0.0-rc.3 to 4.3.1 #3

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

[Snyk] Upgrade workbox-build from 4.0.0-rc.3 to 4.3.1 #3

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade workbox-build from 4.0.0-rc.3 to 4.3.1.

ℹ️ 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 7 versions ahead of your current version.
  • The recommended version was released 3 years ago, on 2019-05-01.
Release notes
Package name: workbox-build
  • 4.3.1 - 2019-05-01

    🐛 What's Fixed?

    workbox-broadcast-update

    • Fixed a bug where some private symbols were not being properly exported from workbox-core, which prevented workbox-broadcast-update from notifying on navigation requests. [#2050]
  • 4.3.0 - 2019-04-15

    🎉 What's New?

    workbox-background-sync

    • Adds a new getAll() method to the Queue class. This can be used to get a list of all unexpired entries in a given queue without removing them. This is useful in situations where replaying the queue is not possible (the user is offline), but you want to show information about the queue to the user. [#2018]

    🐛 What's Fixed?

    Build Tools

    • Fixes a bug where the workbox namespace was used before it was defined, when navigationPreload: true. [#2007]
    • Properly passes in a custom channel name when using the broadcastUpdate option in runtimeCaching. [#2017]

    workbox-background-sync

    • Fixes a bug in which a Request wasn't being clone()ed before re-adding it to the queue. [#2014]
    • Ensures that when a navigation request is stored in the queue, it's serialized with a mode of same-origin. [#2015]

    Thanks!

    Special thanks to @ merrywhether and @ tarjei for contributions that went into this release.

  • 4.2.0 - 2019-04-03

    🎉 What's New?

    Build Tools

    • Adds a new navigationPreload config property (defaulting to false) to workbox-build's generateSW and generateSWString modes, which would also expose it to the wrappers like workbox-cli and workbox-webpack-plugin. [#1981]

    workbox-core

    • Adds workbox.core.cacheNames.prefix and workbox.core.cacheNames.suffix for accessing the current prefix and suffix used in generating cache names. [#2001]

    • Adds a new cacheKeyWillBeUsed lifecycle callback. This allows developers to override the default cache key for reads or writes (or both). [#1990]

    The interface for the callback looks like:

    async function cacheKeyWillBeUsed({request, mode}) {
  // request is the default Request object that would otherwise be used as the cache key.
  // mode is either 'read' or 'write', depending on whether it's a read or a write.
  // Return either a string, or a Request whose url property will be used as the cache key.
  // Returning the original request will make this a no-op.
}

    🐛 What's Fixed?

    workbox-webpack-plugin

    • Convert source to Buffer when getting asset's hash, improving compatibility with some webpack loaders [#1966].
    • Added sorting before generating a hash in the precache manifest. [#1973]

    Thanks!

    Special thanks to @ merrywhether, @ 3846masa and @ el for contributions that went into this release.

  • 4.1.1 - 2019-03-15

    🐛 What's Fixed?

    workbox-window

    • The removeEventListener() method of the Workbox class would throw due to an implementation error, this has been fixed. [#1963]

    • If, at registration time, there was already both an active and waiting service worker with the same script URL as the one being registered, calling getSW() or messageSW() after registration would target the active service worker rather than the waiting service worker. The intended behavior is that the target service worker associated with a Workbox instance is always the most recently registered service worker with a matching script URL. These methods now target the waiting service worker [#1961]

    Thanks!

    Special thanks to @ donavon for contributions that went into this release.

  • 4.1.0 - 2019-03-07

    🎉 What's New?

    workbox-build

    • When using the generateSW option to build your service worker, a message listener is now added to the service worker output, which allows you to invoke skipWaiting() from the window via postMessage() [#1929].

    🐛 What's Fixed?

    workbox-window

    • When calling messageSW() after an updated service worker is found, it would send the message to the service worker currently controlling the page. This has been fixed [#1941].

    workbox-precaching

    • Plugins implementing the cacheDidUpdate method were not properly bound, and would fail in some cases. This has been fixed [#1678].

    workbox-background-sync

    • If requests were added to a backgroundSync.Queue queue due to server error rather than network error, those requests would be retried immediately, which could lead to an infinite loop. This has been fixed [#1943]

    • The backgroundSync.Queue class used to store Request bodies as Blob objects in IndexedDB, but this does not work in Safari. All request bodies are now stored as ArrayBuffer objects [#1932].

    workbox-broadcast-update

    • If the the BroadcastCacheUpdate instance is passed an install event (which happens when using it as a precache plugin) rather than a fetch event, it would error. This has been fixed [#1938].
  • 4.0.0 - 2019-02-27
    Read more
  • 4.0.0-rc.4 - 2019-02-26

    The latest RC release of Workbox v4 includes the following developer-visible changes, in addition to all the changes from the previous pre-releases.

    🐛 What's Fixed?

    workbox-precaching

    • Fixed a bug where precached assets would not trigger the cacheDidUpdate callback because the now contain a __WB_REVISION__ URL parameter. [#1914]

    workbox-routing

    • Fixed a bug where the message listener add via addCacheListener would throw an error if a message event was received where the event.data property was not an object. [#1913]
  • 4.0.0-rc.3 - 2019-02-19

    The latest RC release of Workbox v4 includes the following developer-visible changes, in addition to all the changes from the previous pre-releases.

    🎉 What's New?

    workbox-window

    • Lifecycle events dispatched by the Workbox class now include an isUpdate property. This property can be used to distinguish lifecycle events in the follow scenarios: 1) the very first service worker installation (isUpdate === undefined), 2) an update from a previous service worker version (isUpdate === true).

    • The waiting event dispatched by the Workbox class will now include a wasWaitingBeforeRegistration flag in the event that there was already a service worker waiting when the current service worker was registered. When this is true, it typically means there are other open tabs preventing the service worker from activating (or the user is reloading the current tab). See The Service Worker Lifecycle: skip the waiting phase for more details on why this can happen. [#1905]

    🐛 What's Fixed?

    workbox-routing

    • The message event listener added via addCacheListener() now no longer requires event.data.metadata to equal workbox-window. This allows developers not using workbox-window to still be able to send cache messages to their service worker. [#1906]
from workbox-build GitHub release notes
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

🛠 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