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
Responseis the name used in our root export but the native fetch API adds window.Response as part of that standard. What is the best way to mitigate conflict with this? Rename the export? Ideas? How should we communicate this change?
Activity
amanssit commentedon Jul 26, 2019
Hi @ryanve I am also getting this issue. Response.js Response object getting conflicts with fetch Response.
ryanve commentedon Aug 8, 2019
Ok I'll have to do a new version with a new export name. I'll post here when I do!
ryanve commentedon Aug 8, 2019
noConflictrestores the fetchResponseand returns a reference to the librarySee
noConflictin the source to see how it works : )@amanssit how does that work for you for now?
Clarify noConflict documentation re #76
Clarify noConflict documentation re #76 (#79)