Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.3.3
->^2.0.0
Release Notes
bitinn/node-fetch
v2.3.0
Compare Source
AbortSignal
support, with README example.Location
header during redirect by rejecting them explicitly withFetchError
.browser.js
to support react-native environment, whereself
isn't available globally.v2.2.1
Compare Source
compress
flag shouldn't overwrite existingAccept-Encoding
header.import
rules, wherePassThrough
etc. doesn't have a named export when using node <10 and--exerimental-modules
flag.v2.2.0
Compare Source
ArrayBuffer
view types--experimental-modules
mode; deprecate.es.js
file__esModule
property to the exports objectv2.1.2
Compare Source
Body
methods to work onArrayBuffer
-backedBody
objectsBody
methods when the accumulatedBuffer
exceeds the maximum sizeHost
headers with any casingfetch()
from TypeScript inbrowser.js
v2.1.1
Compare Source
Fix packaging errors in v2.1.0.
v2.1.0
Compare Source
body
of afetch()
orRequest
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 responsesv2.0.0
Compare Source
This is a major release. Check our upgrade guide for an overview on some key differences between v1 and v2.
General changes
require('node-fetch/lib/response')
etc. is now unsupported; userequire('node-fetch').Response
or ES6 module importsObject.prototype.toString()
on Headers, Requests, and Responses return correct class stringsencoding
module is now optional (alpha.7)import
node-fetch by exposing default (alpha.9)HTTP requests
Content-Length
if we can be sure our information is correct (per spec)whatwg-url
package orrequire('url').URL
in Node.js 7+Response and Request classes
response.text()
no longer attempts to detect encoding, instead always opting for UTF-8 (per spec); useresponse.textConverted()
for the v1 behaviorresponse.json()
throw error instead of returning an empty object on 204 no-content respose (per spec; reverts behavior changed in v1.6.2)GET
orHEAD
Request is constructed with a non-null body (per spec)response.arrayBuffer()
(also applies to Requests)response.blob()
(also applies to Requests)URLSearchParams
is now accepted as a bodyresponse.json()
json parsing error asFetchError
null
bodyHeaders class
headers.getAll()
; makeget()
return all headers delimited by commas (per spec)Documentation
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!
".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.