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.

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

remove fetch polyfill #179

Open
adamkasprowicz opened this issue Jul 4, 2019 · 2 comments
Open

remove fetch polyfill #179

adamkasprowicz opened this issue Jul 4, 2019 · 2 comments

Comments

@adamkasprowicz
Copy link
Contributor

No description provided.

@developit
Copy link

Hiya - I've been tracking down a large bundle size problem and noticed a number of copies of whatwg-fetch, of which Keen's embedded copy was one. Do you have a timeline on when this might be possible to implement?

FWIW another option you may want to consider is unfetch (disclaimer: I am the author). It looks like Keen only uses basic fetch functionality, in which case just replacing whatwg-fetch with unfetch would trim somewhere between 3 and 10kb off your library size without worrying about browser support.

@stof
Copy link
Contributor

stof commented May 4, 2020

including unfetch as a polyfill would be a bad news: it would also affect projects wanting to use more complex fetch features (unless the feature detection of these projects accounts for the partial implementation of unfetch)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants