An in-range update of workbox-webpack-plugin is breaking the build 🚨

greenkeeper[bot] commented 6 years ago

Version 3.3.1 of workbox-webpack-plugin was just published.

Branch	Build failing 🚨
Dependency	workbox-webpack-plugin
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

workbox-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **ci/circleci: test** CircleCI is running your tests [Details](https://circleci.com/gh/EZtouch/EZGame/542?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ❌ **ci/circleci: build** Your tests failed on CircleCI [Details](https://circleci.com/gh/EZtouch/EZGame/543?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

After pinning to 3.3.0 your tests are passing again. Downgrade this dependency 📌.

greenkeeper[bot] commented 6 years ago

Version 3.4.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 6 years ago

Version 3.5.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

Workbox v3.5.0

🎉 What's New?

More customization when generating a service worker

Developers who use Workbox to generate their service worker (using the CLI, Node interface, or webpack plugin) can now take advantage of some additional options:

Setting offlineGoogleAnalytics: true will automatically add code to initialize Workbox's offline Google Analytics support in the generated service worker.
Both fetchOptions and matchOptions can now be used when configuring a runtimeCaching route, and those values will be passed through when constructing the corresponding Workbox caching strategy. Many thanks to @peterjosling for contributing this in #1608.
Using a custom plugin within a runtimeCaching route is now possible, thanks to enhancements made by @tsirlucas in #1598.

Here's a snippet of Workbox's build configuration, showing off all of the new features:

{
  // ... other options ...
  offlineGoogleAnalytics: true,
  runtimeCaching: {[
    urlPattern: /abc/,
    handler: 'staleWhileRevalidate',
    options: {
      fetchOptions: {
        mode: 'no-cors',
      },
      matchOptions: {
        ignoreSearch: true,
      },
      plugins: [{
        cacheDidUpdate: async ({cacheName, request, oldResponse, newResponse}) => {
          // Do something in your custom plugin.
        },
      }],
    },
  ]},
}

Support for the `PATCH` method in Workbox's router

Developers who need to match HTTP PATCH requests using Workbox's router can now do so, thanks to @kevin-brotcke's change in #1618.

Note that non-GET requests can't be added to a cache, so this is most useful when used alongside a network-only strategy configured with the Workbox background sync plugin, in order to retry failed PATCH requests once the network becomes available.

`workbox.core.registerQuotaErrorCallback` is now publicly visible

Due to a scoping error, the workbox.core.registerQuotaErrorCallback() function was previously not exposed. This is now public, matching the documented interface. Thanks to @Tronil for pointing out this discrepancy in #1616.

📖 Learn More

Check out our docs @ developers.google.com/web/tools/workbox/

greenkeeper[bot] commented 6 years ago

The devDependency workbox-webpack-plugin was updated from 3.5.0 to 3.6.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for Workbox v3.6.1

🎉 What's New?

Added the `disable()` method to `workbox.navigationPreload`

workbox.navigationPreload provides an enable() method to enable navigation preload, but it did not provide a way to disable it (without invoking the underlying service worker APIs). Now developers can call workbox.navigationPreload.disable() to disable navigation preload. (#1651)

The `method` option can now be used for runtime caching via `generateSW()`

Incorrect validation logic was preventing the method option from being used by runtime caching configuration in generateSW(). Thanks to @chrisdns, this has been fixed! (#1638)

Bug fixes and ergonomic improvements

Using workbox.expiration.Plugin with purgeOnQuotaError set to true would result in an error. Thanks to @salmoro for discovering and fixing the issue! (#1643).
Plugin lifecycle callbacks previously were not called with the event that triggered them, so developers writing custom plugins could not access any information about the event in those callback. Now all plugin callback are passed the event object (when available). (#1640)
The workbox-streams package's strategy() method is exposed on the browser build of workbox.streams that gets loaded by the workbox-sw loader, but it wasn't exported by the module in a way that was accessible to module bundlers. Now it's possible to import {strategy} from workbox-streams/strategy.mjs. (#1635).

📖 Learn More

Check out our docs @ developers.google.com/web/tools/workbox/

greenkeeper[bot] commented 6 years ago

The devDependency workbox-webpack-plugin was updated from 3.6.1 to 3.6.2.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

The devDependency workbox-webpack-plugin was updated from 3.6.2 to 3.6.3.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for Workbox v3.6.3

🐛 What's Fixed?

This release fixes an issue (#1677) that several users have reported, triggered by precaching a URL that returns a 30x redirect to another URL. For instance, having '/index.html' listed in your precache manifest can trigger this issue, if your web server responds to requests for '/index.html' with a 301 redirect to the destination URL '/'. When the issue manifests itself, the final, redirect content ends up being served with an incorrect Content-Type: response header, which can in turn lead problems displaying that cached content.

If you do use 30x redirects for some of your URLs, we recommend updating to this latest release of Workbox.

In order to "clear out" the problematic content that was previously precached with an incorrect Content-Type, after updating Workbox, you can deploy a small change to URLs that you know are affected (i.e. make any change to your '/index.html' file, if that's being fulfilled with a 30x redirect).

It's also possible to force all previously cached entries to be precached again by changing the cacheId option in "generate SW" mode, or by including

workbox.core.setCacheNameDetails({precache: 'my-new-id'});

in your service worker source file in "inject manifest" mode.

📖 Learn More

Check out our docs @ developers.google.com/web/tools/workbox/

EZtouch / EZGame