Open danielroe opened 4 years ago
We do transpile ky (src). Can you please share some more info about error?
Sure. I'll prepare a reproduction. It's worth noting that the error only shows up in production - not in dev.
I have written an almost-drop-in replacement for ky + this module that does work in IE. As I recall the issue was ky's implementation of the Headers class. I'm not suggesting changing @nuxt/http
but it is worth noting in the docs.
Using ky is a little bit disappointing indeed... We may replace in next major version. Would you mind opening docs PR for notice? Later-one can check IE issue on VM and possible fix
Unfortunately this is a game breaker for me and I will have to switch back to axios now :/
@pi0 do you have a specific library in mind for the next mayor version?
@jloewe Most likely building on top of native fetch or an in-house (nuxt-contrib) project for universally using.
@pi0 would you like a PR to refactor this module not to use ky
?
I vote 👍 to remove ky
here and only depend on fetch
. I let @pi0 confirm, thank you for your help @danielroe 💚
Hi @Atinux, @pi0 Can I refactor this module to use https://github.com/nuxt-contrib/ohmyfetch ?
Version
v0.5.11
Reproduction link
https://github.com/danielroe/nuxt-ie-http
See also browser support statement in
ky
READMESteps to reproduce
Although Nuxt polyfills
unfetch
in IE,ky
uses an implementation of the header class that isn't compatible with IE 11.Probably worth mentioning in the docs.
What is expected ?
IE11 support or a mention in the docs
What is actually happening?
No mention