fix: use native abort controller if available (#5)

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.
jacobheun · Aug 31, 2020 · db1fd14 · db1fd14
1 parent faf310e
commit db1fd14
Show file tree

Hide file tree

Showing 6 changed files with 85 additions and 136 deletions.
diff --git a/abort-controller.browser.js b/abort-controller.browser.js
diff --git a/abort-controller.js b/abort-controller.js
diff --git a/index.js b/index.js
@@ -1,4 +1,4 @@
-const AbortController = require('./abort-controller')
+const AbortController = require('native-abort-controller')
 
 /**
  * Takes an array of AbortSignals and returns a single signal.

diff --git a/package-lock.json b/package-lock.json