Currently, the two ways of consuming this package have downsides:
- The
abort-controller export relies on the native implementation in browsers, which will not work in older browsers
- The
abort-controller/polyfill export patches the global AbortController if not present, which can be undesirable
It would be handy to support a ponyfill export which can offer the benefits of both.
(It's likely that this package is used in combination with cross-fetch, which encourages the use of its ponyfill export in its README.)
Currently, the two ways of consuming this package have downsides:
abort-controllerexport relies on the native implementation in browsers, which will not work in older browsersabort-controller/polyfillexport patches the globalAbortControllerif not present, which can be undesirableIt would be handy to support a
ponyfillexport which can offer the benefits of both.(It's likely that this package is used in combination with
cross-fetch, which encourages the use of its ponyfill export in its README.)