Closed greenkeeper[bot] closed 5 years ago
Update to this version instead ๐
See CHANGELOG:
body
of a fetch()
or Request
Headers
object internally with the given case, for compatibility with older servers that incorrectly treated header names in a case-sensitive mannerLocation
header just like non-redirect responsesUpdate to this version instead ๐
Body
methods to work on ArrayBuffer-backed
Body` objectsBody
methods when the accumulated Buffer
exceeds the maximum sizeHost
headers with any casingfetch()
from TypeScript in browser.js
See CHANGELOG.
dependency
node-fetch was updated from 1.7.3
to 2.2.1
.Update to this version instead ๐
See CHANGELOG.
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
dependency
node-fetch was updated from 1.7.3
to 2.3.0
.Update to this version instead ๐
See CHANGELOG.
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
Version 2.0.0 of node-fetch was just published.
The version 2.0.0 is not covered by your current version range.
If you donโt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of node-fetch.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donโt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
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: