All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
2.0.3 (2020-03-12)
- Add license to comment lifted from request (9a2fadb)
2.0.2 (2017-08-15)
2.0.1 (2017-05-24)
- json: improve JSON parse error reporting (1c810df)
2.0.0 (2017-05-06)
- version: force bump to 2.0 (39c5d50)
- version: tooling got confused, so hitting 2.0.0 for reals now
1.0.1 (2017-05-06)
1.0.0 (2017-04-26)
- proj: initial fork changes (0a190a8)
- proj: this renames the library altogether
This is a major release. Check our upgrade guide for an overview on some key differences between v1 and v2.
- Major: Node.js 0.10.x and 0.12.x support is dropped
- Major:
require('node-fetch/lib/response')
etc. is now unsupported; userequire('node-fetch').Response
or ES6 module imports - Enhance: start testing on Node.js 4, 6, 7
- Enhance: use Rollup to produce a distributed bundle (less memory overhead and faster startup)
- Enhance: make
Object.prototype.toString()
on Headers, Requests, and Responses return correct class strings - Other: rewrite in ES2015 using Babel
- Other: use Codecov for code coverage tracking
- Major: overwrite user's
Content-Length
if we can be sure our information is correct (per spec) - Fix: support WHATWG URL objects, created by
whatwg-url
package orrequire('url').URL
in Node.js 7+
- Major:
response.text()
no longer attempts to detect encoding, instead always opting for UTF-8 (per spec); useresponse.textConverted()
for the v1 behavior - Major: make
response.json()
throw error instead of returning an empty object on 204 no-content respose (per spec; reverts behavior changed in v1.6.2) - Major: internal methods are no longer exposed
- Major: throw error when a
GET
orHEAD
Request is constructed with a non-null body (per spec) - Enhance: add
response.arrayBuffer()
(also applies to Requests) - Enhance: add experimental
response.blob()
(also applies to Requests) - Fix: fix Request and Response with
null
body
- Major: remove
headers.getAll()
; makeget()
return all headers delimited by commas (per spec) - Enhance: make Headers iterable
- Enhance: make Headers constructor accept an array of tuples
- Enhance: make sure header names and values are valid in HTTP
- Fix: coerce Headers prototype function parameters to strings, where applicable
- Enhance: more comprehensive API docs
- Enhance: add a list of default headers in README
- Enhance: error handling document to explain
FetchError
design - Fix: support
form-data
2.x releases (requiresform-data
>= 2.1.0)
- Enhance: minor document update
- Fix: response.json() returns empty object on 204 no-content response instead of throwing a syntax error
- Fix: if
res.body
is a non-stream non-formdata object, we will callbody.toString
and send it as a string - Fix:
counter
value is incorrectly set tofollow
value when wrapping Request instance - Fix: documentation update
- Enhance: added
res.buffer()
api for convenience, it returns body as a Node.js buffer - Enhance: better old server support by handling raw deflate response
- Enhance: skip encoding detection for non-HTML/XML response
- Enhance: minor document update
- Fix: HEAD request doesn't need decompression, as body is empty
- Fix:
req.body
now accepts a Node.js buffer
- Fix: handle 204 and 304 responses when body is empty but content-encoding is gzip/deflate
- Fix: allow resolving response and cloned response in any order
- Fix: avoid setting
content-length
whenform-data
body use streams - Fix: send DELETE request with content-length when body is present
- Fix: allow any url when calling new Request, but still reject non-http(s) url in fetch
- Fix: allow node.js core to handle keep-alive connection pool when passing a custom agent
- Fix: redirect mode
manual
should work even when there is no redirection or broken redirection
- Enhance: rejected promise now use custom
Error
(thx to @pekeler) - Enhance:
FetchError
containserr.type
anderr.code
, allows for better error handling (thx to @pekeler) - Enhance: basic support for redirect mode
manual
anderror
, allows for location header extraction (thx to @jimmywarting for the initial PR)
- Fix: wrapping Request instance with FormData body again should preserve the body as-is
- Enhance: Request and Response now have
clone
method (thx to @kirill-konshin for the initial PR) - Enhance: Request and Response now have proper string and buffer body support (thx to @kirill-konshin)
- Enhance: Body constructor has been refactored out (thx to @kirill-konshin)
- Enhance: Headers now has
forEach
method (thx to @tricoder42) - Enhance: back to 100% code coverage
- Fix: better form-data support (thx to @item4)
- Fix: better character encoding detection under chunked encoding (thx to @dsuket for the initial PR)
- Fix: make sure
Content-Length
header is set when body is string for POST/PUT/PATCH requests - Fix: handle body stream error, for cases such as incorrect
Content-Encoding
header - Fix: when following certain redirects, use
GET
on subsequent request per Fetch Spec - Fix:
Request
andResponse
constructors now parse headers input usingHeaders
- Enhance: allow auto detect of form-data input (no
FormData
spec on node.js, this is form-data specific feature)
- Enhance: allow custom host header to be set (server-side only feature, as it's a forbidden header on client-side)
- Enhance: now
fetch.Request
is exposed as well
- Enhance:
Headers
now normalizedNumber
value toString
, prevent common mistakes
- Enhance: now fetch.Headers and fetch.Response are exposed, making testing easier
- Fix:
Headers
should only supportString
andArray
properties, and ignore others
- Enhance: now req.headers accept both plain object and
Headers
instance
- Enhance: timeout now also applies to response body (in case of slow response)
- Fix: timeout is now cleared properly when fetch is done/has failed
- Fix: less greedy content-type charset matching
- Fix: when
follow = 0
, fetch should not follow redirect - Enhance: update tests for better coverage
- Enhance: code formatting
- Enhance: clean up doc
- Enhance: test iojs support
- Enhance: timeout attached to socket event only fire once per redirect
- Fix: response size limit should reject large chunk
- Enhance: added character encoding detection for xml, such as rss/atom feed (encoding in DTD)
- Fix: added res.ok per spec change
- Enhance: better test coverage and doc
- Major: initial public release