npm gzip size downloads travis


Tiny 500b fetch “barely-polyfill”

🤔 What’s Missing?


For use with node and npm:

npm install --save unfetch

Otherwise, grab it from unpkg.com/unfetch.

Usage: As a Polyfill

This automatically “installs” unfetch as window.fetch() if it detects Fetch isn’t supported:

import 'unfetch/polyfill'

// fetch is now available globally!
  .then( r => r.json() )
  .then( data => console.log(data) )

This polyfill version is particularly useful for hotlinking from unpkg:

<script src="https://unpkg.com/unfetch/polyfill"></script>
  // now our page can use fetch!

Usage: As a Ponyfill

With a module bundler like rollup or webpack, you can import unfetch to use in your code without modifying any globals:

// using JS Modules:
import fetch from 'unfetch'

// or using CommonJS:
var fetch = require('unfetch')

// usage:
  .then( r => r.json() )
  .then( data => console.log(data) )

The above will always return unfetch(). (even if window.fetch exists!)

There’s also a UMD bundle available as unfetch/dist/unfetch.umd.js, which doesn’t automatically install itself as window.fetch.

Examples & Demos

Real Example on JSFiddle ➡️

// simple GET request:
  .then( r => r.text() )
  .then( txt => console.log(txt) )

// complex POST request with JSON, headers:
fetch('/bear', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  body: JSON.stringify({ hungry: true })
}).then( r => {
  return r.json();


While one of Unfetch’s goals is to provide a familiar interface, its API may differ from other fetch polyfills/ponyfills. One of the key differences is that Unfetch focuses on implementing the fetch() API, while offering minimal (yet functional) support to the other sections of the Fetch spec, like the Headers class or the Response class. Unfetch’s API is organized as follows:

fetch(url: string, options: Object)

This function is the heart of Unfetch. It will fetch resources from url according to the given options, returning a Promise that will eventually resolve to the response.

Unfetch will account for the following properties in options:

response Methods and Attributes

These methods are used to handle the response accordingly in your Promise chain. Instead of implementing full spec-compliant Response Class functionality, Unfetch provides the following methods and attributes:


Returns true if the request received a status in the OK range (200-299).


Contains the status code of the response, e.g. 404 for a not found resource, 200 for a success.


A message related to the status attribute, e.g. OK for a status 200.


Will return another Object with the same shape and content as response.

response.text(), response.json(), response.blob()

Will return the response content as plain text, JSON and Blob, respectively.


Again, Unfetch doesn’t implement a full spec-compliant Headers Class, emulating some of the Map-like functionality through its own functions: * headers.keys: Returns an Array containing the key for every header in the response. * headers.entries: Returns an Array containing the [key, value] pairs for every Header in the response. * headers.get(key): Returns the value associated with the given key. * headers.has(key): Returns a boolean asserting the existence of a value for the given key among the response headers.


Adapted from the GitHub fetch polyfill readme.

The fetch specification differs from jQuery.ajax() in mainly two ways that bear keeping in mind:

fetch('/users', {
  credentials: 'include'
  .then( checkStatus )
  .then( r => r.json() )
  .then( data => {

function checkStatus(response) {
  if (response.ok) {
    return response;
  } else {
    var error = new Error(response.statusText);
    error.response = response;
    return Promise.reject(error);


First off, thanks for taking the time to contribute! Now, take a moment to be sure your contributions make sense to everyone else.

Reporting Issues

Found a problem? Want a new feature? First of all see if your issue or idea has already been reported. If it hasn’t, just open a new clear and descriptive issue.

Submitting pull requests

Pull requests are the greatest contributions, so be sure they are focused in scope, and do avoid unrelated commits.

💁 Remember: size is the #1 priority.

Every byte counts! PR’s can’t be merged if they increase the output size much.


MIT License © Jason Miller