fix(deps): update dependency whatwg-fetch to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
whatwg-fetch	^2.0.0 -> ^3.0.0

---

Release Notes

github/fetch

v3.6.2

Compare Source

v3.6.1

Compare Source

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 https://github.com/github/fetch/pull/914

v3.6.0

Compare Source

Bug fixes:

• Improve error message if a header contains an invalid character -- https://github.com/github/fetch/pull/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 -- https://github.com/github/fetch/pull/897 Thank you for the contribution @​tkrotoff

• Represent non-stringified JSON request body as an [object Object] string --https://github.com/github/fetch/pull/8811 Thank you for the contribution @​kettanaito

v3.5.0

Compare Source

Added a work-around for projects which use core-js -- https://github.com/github/fetch/issues/748

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

Compare Source

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

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. -- https://github.com/github/fetch/pull/814

Bug fixes:

• Fixed the "self is not defined" error that was reported for NodeJS applications - https://github.com/github/fetch/pull/794

• Reverted the DOMException handling refactor as the original code fixed issues in old Android browsers - https://github.com/github/fetch/pull/797

• Response.arrayBuffer() now always resolve with a ArrayBuffer as per the specification. -- https://github.com/github/fetch/pull/816

• Request and Response can now only be called via new (as constructors) as per the specification. -- https://github.com/github/fetch/pull/796

• Headers which are passed as a Headers object no longer have their names normalised as per the specification -- https://github.com/github/fetch/pull/798

Refactor:

• Removed the top-level this to stop warnings being emitted from Rollup. -- https://github.com/github/fetch/pull/815

v3.2.0

Compare Source

Features:

• Add support for no-cache and no-store - https://github.com/github/fetch/pull/795

Bug fixes:

• Fixed the "self is not defined" error that was reported for NodeJS applications - https://github.com/github/fetch/pull/794
• Throw a TypeError if Request or Response functions are called without new - https://github.com/github/fetch/pull/796

Refactor:

• Refactor DOMException handling code to avoid redundant exceptions generation - https://github.com/github/fetch/pull/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. -- https://github.com/github/fetch/pull/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. -- https://github.com/github/fetch/pull/684

• Changed the default status text of a response to align with the specification, the default is now an empty string. -- https://github.com/github/fetch/pull/698

• We now allow exclamation mark as valid header character to align with the specification -- https://github.com/github/fetch/pull/745

• We no longer convert application/octet-stream responses into Blobs if the browser supports ArrayBuffers -- https://github.com/github/fetch/pull/752

• Added compatibility for fetch-mock -- https://github.com/github/fetch/pull/736

• Making a fetch request with an empty string for the url no longer throws a DOMException error in Internet Explorer -- https://github.com/github/fetch/pull/619

• Fixed another Internet Explorer bug to make sure all resolved fetch promises will trigger their promise chains -- https://github.com/github/fetch/pull/575

v3.0.1

Compare Source

v3.0.0: fetch 3.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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.