Hello,
With all major browsers supporting fetch since years ago, and already with the warn about browser support should we make it more explicit from which version of each browser we don't need this polifyll ? Also what about warn users if they try to use it in a browser that already supports fetch ?
Example something like this:
⚠️ Browser Support Notice
Do not use this polyfill if you only target modern browsers.
All currently maintained browsers provide a native, standards-compliant fetch implementation. Including whatwg-fetch in these environments is unnecessary and adds extra bundle size.
Browsers where whatwg-fetch is NOT needed
| Browser |
Minimum version with native fetch |
| Chrome |
42+ |
| Firefox |
39+ |
| Edge (Chromium) |
All versions |
| Edge (Legacy) |
14+ |
| Safari (macOS) |
10.1+ |
| Safari (iOS) |
10.3+ |
| Opera |
29+ |
| Samsung Internet |
4.0+ |
If your supported browser list only includes the versions above (or newer), do not install or import this polyfill.
Hello,
With all major browsers supporting fetch since years ago, and already with the warn about browser support should we make it more explicit from which version of each browser we don't need this polifyll ? Also what about warn users if they try to use it in a browser that already supports fetch ?
Example something like this:
Do not use this polyfill if you only target modern browsers.
All currently maintained browsers provide a native, standards-compliant
fetchimplementation. Includingwhatwg-fetchin these environments is unnecessary and adds extra bundle size.Browsers where
whatwg-fetchis NOT neededfetchIf your supported browser list only includes the versions above (or newer), do not install or import this polyfill.