All Versions
19
Latest Version
Avg Release Cycle
121 days
Latest Release
350 days ago

Changelog History
Page 1

  • v3.5.0 Changes

    November 06, 2020

    โž• Added a work-around for projects which use core-js -- #748

  • v3.4.1 Changes

    September 07, 2020

    Republishing to ensure the dist/fetch.umd.js is up-to-date

  • v3.4.0 Changes

    August 07, 2020

    ๐Ÿ‘‰ Use globalThis as the global object if it exists #822

  • v3.3.1

    August 04, 2020
  • v3.3.0 Changes

    August 04, 2020

    ๐Ÿ”‹ 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 Changes

    July 09, 2020

    ๐Ÿ”‹ 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 Changes

    July 08, 2020

    ๐Ÿ› Bug fix

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

  • v3.1.0 Changes

    June 30, 2020

    ๐Ÿ“š 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

    July 08, 2020
  • v3.0.0 Changes

    September 07, 2018

    ๐Ÿ“ฆ 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.