Skip to content

Explain why we forked the GitHub version #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 10, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,14 @@
# window.fetch polyfill

This is a fork of [GitHub's fetch polyfill](https://github.com/github/fetch). Its purpose is to get [the fetch polyfill used in React Native](https://github.com/facebook/react-native/blob/master/Libraries/Network/fetch.js) closer to the `whatwg` spec without worrying about breaking older browser versions.

For more context, see [the `github/fetch` issue](https://github.com/github/fetch/issues/746) and [the `react-native` issue](https://github.com/facebook/react-native/issues/27741).

---

The `fetch()` function is a Promise-based mechanism for programmatically making
web requests in the browser. This project is a polyfill that implements a subset
of the standard [Fetch specification][], enough to make `fetch` a viable
of the standard [fetch specification](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API), enough to make `fetch` a viable
replacement for most uses of XMLHttpRequest in traditional web applications.

## Table of Contents
Expand Down