node-fetch - npm Package Compare versions

Comparing version 1.1.2 to 1.2.0

CHANGELOG.md

		@@ -8,4 +8,8 @@

		## v1.1.2 (master)
		## v1.2.0 (master)

		- Enhance: now fetch.Headers and fetch.Response are exposed, making testing easier

		## v1.1.2

		- Fix: `Headers` should only support `String` and `Array` properties, and ignore others
		@@ -12,0 +16,0 @@

index.js

		@@ -193,1 +193,3 @@
		Fetch.Promise = global.Promise;
		Fetch.Response = Response;
		Fetch.Headers = Headers;

LIMITS.md


		Known limits
		============
		Known differences
		=================

		@@ -19,2 +19,4 @@ As of 1.x release

		- Only expose `Response` and `Headers` constructors at the moment, we don't see a good use-case for `Request` interface yet.

		- There is currently no built-in caching, as server-side caching varies by use-cases.

package.json

		{
		"name": "node-fetch",
		"version": "1.1.2",
		"version": "1.2.0",
		"description": "A light-weight module that brings window.fetch to node.js and io.js",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -33,3 +33,3 @@

		- See [Known limits](https://github.com/bitinn/node-fetch/blob/master/LIMITS.md) for details.
		- See [Known Differences](https://github.com/bitinn/node-fetch/blob/master/LIMITS.md) for details.
		- If you happen to use a missing feature that `window.fetch` offers, feel free to open an issue.
		@@ -36,0 +36,0 @@ - Pull requests are welcomed too!

test/test.js

		@@ -62,2 +62,7 @@

		it('should expose Headers and Response constructors', function() {
		expect(fetch.Headers).to.equal(Headers);
		expect(fetch.Response).to.equal(Response);
		});

		it('should reject with error if url is protocol relative', function() {
		@@ -64,0 +69,0 @@ url = '//example.com/';

New alerts