Export conflicts with fetch Response

[ryanve]

Response is 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?

• response
• responseJS
• response.js like the npm name
• ... ?

[amanssit]

Hi @ryanve I am also getting this issue. Response.js Response object getting conflicts with fetch Response.

[ryanve]

Ok I'll have to do a new version with a new export name. I'll post here when I do!

[ryanve]

noConflict restores the fetch Response and returns a reference to the library

let R = Response.noConflict() 

See noConflict in the source to see how it works : )

@amanssit how does that work for you for now?