strange dependency requirement uses a random git branch about isomorphic-fetch

[airwin]

agree

[tracker1]

+1 it may be better to publish what-wg fetch client as a separate module in npm, then reference/update against that?

[matthew-andrews]

We switched to that branch to get some basic IE9 cors support (did make a PR for this back to the GitHub polyfill — which wasn't accepted)… plan is to eliminate our need for this which I think is imminent…… (@whererhys do you know if we still IE9?)……

@tracker1 think it's already in npm registry?

[tracker1]

Would probably just refer people to xdomain if you need to support older versions of IE... I didn't know if that specific branch (with IE9 support) was published as a separate module from the github shim.

[aintgoin2goa]

This branch doesn't actually work in any browser if you need CORS with cookies. this line:

https://github.com/matthew-andrews/fetch/blob/master/fetch.js#L246

option should actually be 'include':
https://developer.mozilla.org/en-US/docs/Web/API/Request/credentials

This is a simple fix but there is quite a log of different between githubs fetch and this one, it might be a better idea to refactor out the IE9 stuff into a seperate module or something?

[matthew-andrews]

using the main polyfill as of v2.1.0