This fork supports IE8 with es5-shim, es5-sham and es6-promise.
If you also use JSONP, checkout fetch-jsonp.
Fetch API is still very new and not fully supported in some browsers, so you mayneed to check browser verson as well as if window.fetch
exists. In this case,you can set window.__disableNativeFetch = true
to use AJAX polyfill always.
I'm trying to POST a request (Form) using the fetch polyfill 'whatwg-fetch'. While this works in Chrome and FF, it doesn't seem to work on IE and Edge. Import 'whatwg-fetch'; const dataObject =.
The global fetch
function is an easier way to make web requests and handleresponses than using an XMLHttpRequest. This polyfill is written as closely aspossible to the standard Fetch specification at https://fetch.spec.whatwg.org.
You'll also need a Promise polyfill for older browsers.
Run this to polyfill the global environment at the beginning of your application.
(For a node.js implementation, try node-fetch)
The fetch
function supports any HTTP method. We'll focus on GET and POSTexample requests.
This causes fetch
to behave like jQuery's $.ajax
by rejecting the Promise
on HTTP failure status codes like 404, 500, etc. The response Promise
isresolved only on successful, 200 level, status codes.
The Response
object has a URL attribute for the final responded resource.Usually this is the same as the Request
url, but in the case of a redirect,its all transparent. Newer versions of XHR include a responseURL
attributethat returns this value. But not every browser supports this. The compromiserequires setting a special server side header to tell the browser what URL itjust requested (yeah, I know browsers).
If you want response.url
to be reliable, you'll want to set this header. Theday that you ditch this polyfill and use native fetch only, you can remove theheader hack.
Latest ✔ | Latest ✔ | 8+ ✔ | Latest ✔ | 6.1+ ✔ |