An in-range update of node-fetch is breaking the build 🚨

[greenkeeper]

The dependency node-fetch was updated from 2.2.0 to 2.2.1.

🚨 View failing branch.

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

node-fetch is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v2.2.1

See CHANGELOG.

Commits

The new version differs by 8 commits.

• ac07bf7 2.2.1
• 9a32fd3 ready for release
• 4bc21da doc update
• 5494e19 compress flag should not overwrite accept encoding header
• 91e1c0b avoid named export for compatibility below node 10
• d935121 fix import rule for stream PassThrough
• 8cc909f update readme to add credits and call for collaborators (#540)
• 745a27c README update (#504)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The dependency node-fetch was updated from 2.2.1 to 2.3.0.

Your tests are still failing with this version. Compare changes

Release Notes for v2.3.0

See CHANGELOG.

Commits

The new version differs by 4 commits ahead by 4, behind by 6.

• 5367fe6 v2.3.0 (#548)
• d1ca2df Workaround lack of global context in react-native (#545)
• ecd3d52 Add support for AbortSignal to cancel requests (#539)
• 1daae67 Fix import style to workaround node < 10 and webpack issues. (#544)

See the full diff