Releases: github/fetch

Bug fixes:

• Fixes a bug in v3.6.0 where the syntax used was not ES3 as it has used const
• Fixes a bug in v3.6.0 where String.prototype.includes was used, which is not supported in IE 11

Both were fixed in #914

Bug fixes:

• Improve error message if a header contains an invalid character -- #880 Thank you for the contribution @CarmeloPatti

• Make Response.statusText be an empty string if set to undefined and be 'null' if set to null -- #897 Thank you for the contribution @tkrotoff

• Represent non-stringified JSON request body as an [object Object] string -- #881 Thank you for the contribution @kettanaito

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

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

Use globalThis as the global object if it exists #822

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

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

Bug fix

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