You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an elegant, safe, and effective solution to a common problem, one really worth promoting. With the recent changes, I think its scope has changed. It's not just a browser ponyfill, it's also an isomorphic fetch. What do you think about updating the description to reflect that?
isomorphic-fetch describes itself like this:
Isomorphic WHATWG Fetch API, for Node & Browserify
I think what we've got here is:
Isomorphic WHATWG Fetch API ponyfill for Node, Browserify, and Webpack
For people to find this, I think the most effective thing would be to update the github name and npm description along those lines. The second thing would be to mention Browserify and Webpack in npm keywords and in the body of the readme.
Thoughts?
The text was updated successfully, but these errors were encountered:
Just wanted to say thanks for this module - getting bitten by a broken window.fetch() implementation in Edge 14, and this module really helps get past whatwg-fetch's many refusals to implement a UMD shim.
I've taken a couple steps to promote this library, e.g. matthew-andrews/isomorphic-fetch#93
This is an elegant, safe, and effective solution to a common problem, one really worth promoting. With the recent changes, I think its scope has changed. It's not just a browser ponyfill, it's also an isomorphic fetch. What do you think about updating the description to reflect that?
isomorphic-fetch
describes itself like this:I think what we've got here is:
For people to find this, I think the most effective thing would be to update the github name and npm description along those lines. The second thing would be to mention Browserify and Webpack in npm keywords and in the body of the readme.
Thoughts?
The text was updated successfully, but these errors were encountered: