Update dependency whatwg-fetch to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
whatwg-fetch	1.0.0 -> 3.6.2

---

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

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

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.

v2.0.4

Compare Source

• Support obs-fold as delimiter when parsing raw headers

• Ensure cookies aren't sent if credentials: omit

• Allow status: undefined in Response

v2.0.3

Compare Source

• Accept Array argument in Headers constructor

v2.0.2

Compare Source

• Treat any non-Request arg to new Request() as string url
• Support Tolerance Provision when parsing HTTP headers

v2.0.1

Compare Source

Android 4.0 compatibility:

• Fix reading ArrayBuffer into string on older browsers
• Only define arrayBuffer() if Blob is also supported

v2.0.0

Compare Source

This changes the behavior of Headers regarding handling of headers with multiple values. Most notably, it removes the Headers.getAll() method. This diverges from the native implementations of Chrome and Firefox, since those vendors implement an earlier, now outdated version of the spec. The polyfill now acts more similar to Microsoft Edge implementation.

Consider this Headers object:

var h = new Headers()
h.append('accept', 'text/html')
h.append('accept', 'text/plain')
h.append('content-type', 'application/json')

Before:

• h.get('accept') returned text/html
• h.getAll('accept') returned an array of values
• h.forEach (and other iterables) did distinct iterations for each
  value of the same header

Now:

• h.get('accept') returns text/html,text/plain
• h.getAll() is no more
• h.forEach() (and other iterables) now only do one iteration for each unique header name, regardless of whether it had multiple values

This is in accordance with Section 3.1.2 of the spec, "combine" concept.

v1.1.1

Compare Source

Android 4.0 compatibility:

• Fix reading ArrayBuffer into string on older browsers
• Only define arrayBuffer() if Blob is also supported

v1.1.0

Compare Source

Spec compatibility:

• 1st argument to Request constructor must be string or Request
• Always construct a new Request instance in fetch()
• Always construct a new Headers instance in Response
• Avoid consuming body when cloning
• Add support for TypedArray/DataView as POST body
• ArrayBuffer, TypedArray, and Dataview bodies can now be accessed through any of the arrayBuffer(), text(), or blob() methods
• Default Response status is 200 OK

Other fixes:

• Make X-Request-URL header case-insensitive
• Allow reusing the same GET Request instance multiple times
• Rework parsing of raw response HTTP headers
• Attach FileReader event handlers before calling its read* method

---

Configuration

📅 Schedule: 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, click this checkbox.

---

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

[pull-assistant]

Best reviewed: commit by commit

---

Optimal code review plan

     Update dependency whatwg-fetch to v3

Powered by Pull Assistant. Last update 63c885c ... 63c885c. Read the comment docs.

[vizipi]

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code.
This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

Reviewers with knowledge related to these changes

Match %	Person	Commit Count	Common Files
100.00 %	Chintan Prajapati	2	1

---

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold

---

Committed file ranks

(click to expand)

85.71%[package.json]

[guardrails]

All previously detected findings have been fixed. Good job! 👍🎉

We will keep this comment up-to-date as you go along and notify you of any security issues that we identify.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[guardrails]

⚠️ We detected security issues in this pull request:

Vulnerable Libraries (2)

• open@0.0.5 upgrade to >0.0.5
• js-yaml@3.7.0 upgrade to >=3.13.1

More info on how to fix Vulnerable Libraries in Javascript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.