This repository has been archived by the owner on Feb 19, 2024. It is now read-only.
chore(deps): update dependency whatwg-fetch to v3.6.2 #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.0
->3.6.2
Release Notes
github/fetch
v3.6.2
Compare Source
v3.6.1
Compare Source
Bug fixes:
const
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 tonull
-- https://github.com/github/fetch/pull/897 Thank you for the contribution @tkrotoffRepresent 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-dateCompare 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:
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 aArrayBuffer
as per the specification. -- https://github.com/github/fetch/pull/816Request
andResponse
can now only be called vianew
(as constructors) as per the specification. -- https://github.com/github/fetch/pull/796Headers which are passed as a
Headers
object no longer have their names normalised as per the specification -- https://github.com/github/fetch/pull/798Refactor:
this
to stop warnings being emitted from Rollup. -- https://github.com/github/fetch/pull/815v3.2.0
Compare Source
Features:
Bug fixes:
new
- https://github.com/github/fetch/pull/796Refactor:
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:
fetch
which are not polyfilled. -- https://github.com/github/fetch/pull/734Bug 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 intoBlob
s if the browser supportsArrayBuffers
-- https://github.com/github/fetch/pull/752Added compatibility for
fetch-mock
-- https://github.com/github/fetch/pull/736Making 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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.