Drop IE8 support

I know, I know, it was just added 😃 But still - I’m raising this issue to at least get an official “no” - or maybe someone has a more concrete idea on how to decouple IE8 support / inject the header parsing function?

IE8 support depends on parse-headers, which is an extra 1.5kb browserified+minified. I’m using xhr itself exactly because it is small - ~2kb browserified+minified, so IE8 support effectively doubles the size. Some might say that’s not much, but over here we have to save every byte (building a script for 3rd party sites…). Plus IE8 is not a Real Browser™ anyways.

[naugtur]

The code is on a branch. It’ll get in as soon as other breaking changes for next major are implemented, but this got put on hold a few months ago as my daughter was born and other contributors weren’t too active either. I’ll get back to it eventually.

Feel free to take a look at https://github.com/naugtur/xhr/issues/81 to help push it forward

[pluma]

-1 for dropping IE8 support entirely. I’m currently using xhr in a project that will have to support IE8 for at least another year, maybe longer. I’m also using xhr in arangodbjs, which works fine with IE8 otherwise. Also, IMO xhr’s main selling point is being a browserify substitute for request.

+1 for xhr/ie