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
Fix an issue on some versions of node-fetch where the constructor of the returned response is not Response, but rather a different Body class that does not set the same properties. This caused our cloned response instance to not have a headers property. Now, we check the input Fetch instance for a Response property (like node-fetch does) or try to get it from global (like isomorphic-fetch does) before falling back to response.constructor. To fully override the class (for more complicated scenarios), use the new Response option to withHar.
Internal
Add real tests using Jest. All of node-fetch, isomorphic-fetch, and isomorphic-unfetch are tested. Even though they all use node-fetch, isomorphic-fetch uses an old version, and we may need to test additional integration points (like what properties exist on the default export).