Make module available without polyfill about fetch

[josh]

You might want to checkout
https://github.com/matthew-andrews/isomorphic-fetch

This library is just going to be a standard polyfill implementation.
On Tue, Dec 23, 2014 at 8:34 PM Mark S. Everitt [email protected]
wrote:

It would be nice to be able to require fetch without it being appended to
window in a similar way to the es6-promise polyfill. If fetch can be
assigned to a variable, then this means that when a broken or otherwise
incompatible version of the fetch API become available in a browser, code
that uses fetch won't break.

—
Reply to this email directly or view it on GitHub
#46.

[qubyte]

That module just does the same as this one, but works in Node too. i.e. the behaviour in the browser is identical.

One last try to convince... doing this will allow your users to protect themselves from differences in implementation and changes in spec as browsers evolve.

Else, I can close (or please feel free to).

[qubyte]

This is what I'm using at the moment. Seriously ugly, but has the behaviour I want: https://gist.github.com/qubyte/21cade5e28c924c48bc1

[schickling]

+1

[qubyte]

I put that gist into a library. It has one potential showstopping problem though... It means that the brfs transform must be used globally. https://github.com/qubyte/fetch-ponyfill

[domenic]

@qubyte you can specify transforms on a per-package basis (e.g. in your fetch-ponyfill package.json) to avoid the global-ness.

[qubyte]

@domenic Wow. I really should have realised that. Thanks for the tip!

[josh]

#9 (comment)