Go to file
David Frank 955b0c0719 update doc 2015-01-28 01:20:54 +08:00
lib better test coverage 2015-01-28 01:00:53 +08:00
test better test coverage 2015-01-28 01:00:53 +08:00
.gitignore setup repo 2015-01-26 17:02:34 +08:00
.travis.yml better test coverage 2015-01-28 01:00:53 +08:00
CHANGELOG.md release 0.1.0 2015-01-27 21:13:28 +08:00
LICENSE.md setup repo 2015-01-26 17:02:34 +08:00
LIMITS.md release 0.1.0 2015-01-27 21:13:28 +08:00
README.md update doc 2015-01-28 01:20:54 +08:00
index.js better test coverage 2015-01-28 01:00:53 +08:00
package.json better test coverage 2015-01-28 01:00:53 +08:00

README.md

node-fetch

npm version build status coverage status

A light-weight module that brings window.fetch to node.js

Motivation

I really like the notion of Matt Andrews' isomorphic-fetch: it bridges the API gap between client-side and server-side http requests, so developers have less to worry about.

But I think the term isomorphic is generally misleading: it gives developers a false sense of security that their javascript code will run happily on both controlled server environment as well as uncontrollable user browsers. When the latter is only true for a subset of modern browsers, not to mention quirks in native implementation.

Instead of implementing XMLHttpRequest in node to run browser-specific fetch polyfill, why not go from node's http to fetch API directly? Node has native stream support, browserify build targets (browsers) don't, so underneath they are going to be vastly different anyway.

Hence node-fetch, minimal code for a window.fetch compatible API on node.js runtime.

Features

  • Stay consistent with window.fetch API.
  • Make conscious trade-off when following whatwg fetch spec and stream spec implementation details, document known difference.
  • Use native promise, but allow substituting it with [insert your favorite promise library].

Difference from client-side fetch

  • See Known limits for details.
  • If you happen to use a missing feature that window.fetch offers, feel free to open an issue.
  • Pull requests are welcomed too!

Install

npm install node-fetch --save

Usage

var fetch = require('node-fetch');

// plain text or html

fetch('https://github.com/')
	.then(function(res) {
		return res.text();
	}).then(function(body) {
		console.log(body);
	});

// json

fetch('https://api.github.com/users/github')
	.then(function(res) {
		return res.json();
	}).then(function(json) {
		console.log(json);
	});

// meta

fetch('https://github.com/')
	.then(function(res) {
		console.log(res.status);
		console.log(res.statusText);
		console.log(res.headers.raw());
		console.log(res.headers.get('content-type'));
	});

// post

fetch('http://httpbin.org/post', { body: 'a=1' })
	.then(function(res) {
		return res.json();
	}).then(function(json) {
		console.log(json);
	});

// post with stream

var resumer = require('resumer');
fetch('http://httpbin.org/post', { body: resumer().queue('a=1').end() })
	.then(function(res) {
		return res.json();
	}).then(function(json) {
		console.log(json);
	});

// post with formdata

var FormData = require('form-data');
var form = new FormData();
form.append('a', 1);
fetch('http://httpbin.org/post', { body: form, headers: form.getHeaders() })
	.then(function(res) {
		return res.json();
	}).then(function(json) {
		console.log(json);
	});

See test cases for more examples.

License

MIT

Acknowledgement

Thanks to github/fetch for providing a solid implementation reference.