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

replace isomorphic fetch with whatwg-fetch and node-fetch #3

Merged
merged 1 commit into from
Apr 21, 2016

Conversation

hampsterx
Copy link
Contributor

isomorphic-fetch doesn't work properly with webpack

matthew-andrews/isomorphic-fetch#31 (comment)

@hampsterx hampsterx force-pushed the replace_isomorphic_fetch branch 2 times, most recently from f65500b to d951b0a Compare April 21, 2016 03:31
@coveralls
Copy link

Coverage Status

Coverage decreased (-1.2%) to 92.353% when pulling d951b0a on replace_isomorphic_fetch into 4da4cb3 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-1.2%) to 92.353% when pulling d951b0a on replace_isomorphic_fetch into 4da4cb3 on master.

@hampsterx hampsterx merged commit 75983ea into master Apr 21, 2016
@paulmelnikow
Copy link

You may be interested in taking a look at https://github.com/qubyte/fetch-ponyfill, which is an isomorphic fetch which unlike isomorphic-fetch does not replace the native fetch. It works correctly in Node and the browser, and is compatible with Webpack, and Browserify. It might streamline things for you a bit, since you can just require fetch-ponyfill, and it takes care of whatwg-fetch and node-fetch under the hood.

@hampsterx hampsterx deleted the replace_isomorphic_fetch branch September 19, 2016 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants