Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: use native abort controller if available #5

Merged
merged 1 commit into from
Aug 31, 2020
Merged

fix: use native abort controller if available #5

merged 1 commit into from
Aug 31, 2020

Commits on Aug 28, 2020

  1. fix: use native abort controller if available 

    Some environments like Electron's Renderer process have native browser
APIs available but don't respect the `browser` field in `package.json`.

You also don't always want to use 100% browser or 100% node APIs depending
on your application, so don't make the user choose all or nothing.

Here we switch out `abort-controller` for `native-abort-controller`
which will return the native abort controller if it's available, or the
`abort-controller` polyfill if it is not.
    @achingbrain
    achingbrain committed Aug 28, 2020
    Configuration menu
    Copy the full SHA
    5149de1 View commit details
    Browse the repository at this point in the history