node-fetch/CHANGELOG.md

173 lines
6.1 KiB
Markdown
Raw Normal View History

2015-01-26 01:02:34 -08:00
Changelog
=========
2015-01-27 10:02:27 -08:00
2016-12-05 20:40:23 -08:00
# 2.x release
## v2.0.0-alpha.1
This is a major release. Check [our upgrade guide](https://github.com/bitinn/node-fetch/blob/master/UPGRADE-GUIDE.md) for an overview on some key differences between v1 and v2.
2016-12-05 20:40:23 -08:00
- Major: Node.js 0.10.x support is dropped
- Major: rewrite in transpiled ES2015
- Major: internal methods are no longer exposed
- Major: throw error when a GET/HEAD Request is constructed with a non-null body (per spec)
- Major: `response.text()` no longer attempts to detect encoding, instead always opting for UTF-8 (per spec); use `response.textConverted()` for the old behavior
- Major: make `response.json()` throw error instead of returning an empty object on 204 no-content respose (per spec; reverts behavior set in v1.6.2)
- Major: arrays as parameters to `headers.append` and `headers.set` are joined as a string (per spec)
- 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 `toString()` on Headers, Requests, and Responses return correct IDL class strings
- Enhance: add an option to conform to latest spec at the expense of reduced compatibility
- Enhance: set `Content-Length` header for Buffers as well
- Enhance: add `response.arrayBuffer()` (also applies to Requests)
- Enhance: add experimental `response.blob()` (also applies to Requests)
- 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
- Fix: fix Request and Response with `null` body
- Fix: support WHATWG URL objects, created by `whatwg-url` package or `require('url').URL` in Node.js 7+
- Other: use Codecov for code coverage tracking
2015-01-27 10:02:27 -08:00
# 1.x release
2016-09-25 22:35:30 -07:00
## v1.6.3
2016-09-25 23:03:28 -07:00
- Enhance: error handling document to explain `FetchError` design
2016-09-25 22:35:30 -07:00
- Fix: support `form-data` 2.x releases (requires `form-data` >= 2.1.0)
## v1.6.2
2016-09-24 02:53:04 -07:00
- Enhance: minor document update
- Fix: response.json() returns empty object on 204 no-content response instead of throwing a syntax error
## v1.6.1
2016-08-03 03:02:26 -07:00
2016-09-11 07:37:42 -07:00
- Fix: if `res.body` is a non-stream non-formdata object, we will call `body.toString` and send it as a string
2016-09-11 07:05:32 -07:00
- Fix: `counter` value is incorrectly set to `follow` value when wrapping Request instance
- Fix: documentation update
2016-09-11 07:05:32 -07:00
## v1.6.0
- Enhance: added `res.buffer()` api for convenience, it returns body as a Node.js buffer
2016-08-03 03:02:26 -07:00
- 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
2016-09-11 07:05:32 -07:00
- Fix: `req.body` now accepts a Node.js buffer
2016-08-03 03:02:26 -07:00
## v1.5.3
2016-05-25 11:27:25 -07:00
- Fix: handle 204 and 304 responses when body is empty but content-encoding is gzip/deflate
2016-05-25 11:27:25 -07:00
- Fix: allow resolving response and cloned response in any order
2016-09-11 07:05:32 -07:00
- Fix: avoid setting `content-length` when `form-data` body use streams
2016-05-25 11:27:25 -07:00
- 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
## v1.5.2
2016-05-06 05:02:07 -07:00
- Fix: allow node.js core to handle keep-alive connection pool when passing a custom agent
## v1.5.1
2016-04-12 11:58:04 -07:00
- Fix: redirect mode `manual` should work even when there is no redirection or broken redirection
2016-04-12 11:59:43 -07:00
## v1.5.0
2016-04-05 10:32:37 -07:00
- Enhance: rejected promise now use custom `Error` (thx to @pekeler)
- Enhance: `FetchError` contains `err.type` and `err.code`, allows for better error handling (thx to @pekeler)
2016-04-05 11:49:23 -07:00
- Enhance: basic support for redirect mode `manual` and `error`, allows for location header extraction (thx to @jimmywarting for the initial PR)
2016-04-05 10:32:37 -07:00
## v1.4.1
2016-03-23 00:32:31 -07:00
- Fix: wrapping Request instance with FormData body again should preserve the body as-is
## v1.4.0
2016-03-19 03:57:41 -07:00
- 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)
## v1.3.3
2015-09-28 07:48:11 -07:00
- 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` and `Response` constructors now parse headers input using `Headers`
## v1.3.2
- Enhance: allow auto detect of form-data input (no `FormData` spec on node.js, this is form-data specific feature)
## v1.3.1
2015-06-03 21:21:05 -07:00
- Enhance: allow custom host header to be set (server-side only feature, as it's a forbidden header on client-side)
## v1.3.0
2016-09-11 07:05:32 -07:00
- Enhance: now `fetch.Request` is exposed as well
2015-06-03 21:21:05 -07:00
## v1.2.1
2015-05-03 21:07:38 -07:00
- Enhance: `Headers` now normalized `Number` value to `String`, prevent common mistakes
## v1.2.0
2015-05-03 03:07:20 -07:00
- Enhance: now fetch.Headers and fetch.Response are exposed, making testing easier
## v1.1.2
2015-04-28 21:17:18 -07:00
- Fix: `Headers` should only support `String` and `Array` properties, and ignore others
## v1.1.1
2015-04-22 08:36:11 -07:00
- Enhance: now req.headers accept both plain object and `Headers` instance
## v1.1.0
2015-04-16 22:31:58 -07:00
- 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
## v1.0.6
2015-03-23 21:31:04 -07:00
- Fix: less greedy content-type charset matching
## v1.0.5
2016-09-11 07:05:32 -07:00
- Fix: when `follow = 0`, fetch should not follow redirect
- Enhance: update tests for better coverage
- Enhance: code formatting
- Enhance: clean up doc
## v1.0.4
2015-02-01 05:19:07 -08:00
2015-02-06 03:15:37 -08:00
- Enhance: test iojs support
2015-02-01 05:19:07 -08:00
- Enhance: timeout attached to socket event only fire once per redirect
## v1.0.3
- Fix: response size limit should reject large chunk
- Enhance: added character encoding detection for xml, such as rss/atom feed (encoding in DTD)
## v1.0.2
2015-01-27 20:17:12 -08:00
- Fix: added res.ok per spec change
2015-01-27 10:02:27 -08:00
## v1.0.0
- Enhance: better test coverage and doc
2015-01-27 05:13:28 -08:00
# 0.x release
2015-01-26 01:02:34 -08:00
2015-01-27 05:13:28 -08:00
## v0.1
2015-01-26 01:02:34 -08:00
- Major: initial public release