v3.4.0

Compare Source

Use globalThis as the global object if it exists #​822

v3.3.1

Compare Source

v3.3.0

Compare Source

Features:

• Updated documentation for AbortController to recommend a polyfill which is spec-compliant and fully synchronous. -- #​814

Bug fixes:

• Fixed the "self is not defined" error that was reported for NodeJS applications - #​794

• Reverted the DOMException handling refactor as the original code fixed issues in old Android browsers - #​797

• Response.arrayBuffer() now always resolve with a ArrayBuffer as per the specification. -- #​816

• Request and Response can now only be called via new (as constructors) as per the specification. -- #​796

• Headers which are passed as a Headers object no longer have their names normalised as per the specification -- #​798

Refactor:

• Removed the top-level this to stop warnings being emitted from Rollup. -- #​815

v3.2.0

Compare Source

Features:

• Add support for no-cache and no-store - #​795

Bug fixes:

• Fixed the "self is not defined" error that was reported for NodeJS applications - #​794
• Throw a TypeError if Request or Response functions are called without new - #​796

Refactor:

• Refactor DOMException handling code to avoid redundant exceptions generation - #​797

v3.1.1

Compare Source

Bug fix

-- check if Content-Type header exists prior to examining the value #​792

v3.1.0

Compare Source

Documentation:

• Added documentation on features of fetch which are not polyfilled. -- #​734

Bug fixes:

• Empty header names used to not throw an error which was not compliant with the specification. They now throw a TypeError, the same as Chrome, Firefox and Safari do. -- #​684

• Changed the default status text of a response to align with the specification, the default is now an empty string. -- #​698

• We now allow exclamation mark as valid header character to align with the specification -- #​745

• We no longer convert application/octet-stream responses into Blobs if the browser supports ArrayBuffers -- #​752

• Added compatibility for fetch-mock -- #​736

• Making a fetch request with an empty string for the url no longer throws a DOMException error in Internet Explorer -- #​619

• Fixed another Internet Explorer bug to make sure all resolved fetch promises will trigger their promise chains -- #​575

v3.0.1

Compare Source

v3.0.0

Compare Source

• The whatwg-fetch package is now a module with exports. The following methods/classes are available:

  • fetch
  • Headers
  • Request
  • Response
  • DOMException

  All exports except for DOMException represent the polyfill implementations, not the native variants if they are available.

  This library still automatically acts like a polyfill if native window.fetch is unavailable; there is currently no way to use it as a ponyfill.

• Change credentials default value omit → same-origin to match the updated spec.

• fetch() and new Request() now accept the signal parameter to accept an AbortSignal.

• Join multiple header values with ,<space> instead of , to match other browsers.

• Convert any Request/Response unsupported body type to a string to match the spec.

• Flow type definitions are now included in the package.