-
Notifications
You must be signed in to change notification settings - Fork 147
feat(package.json): Update dependency whatwg-fetch to v3.4.1 #480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6957687
to
8e875fc
Compare
b07261e
to
0a7de26
Compare
0a7de26
to
3b43103
Compare
716612d
to
de65a46
Compare
de65a46
to
2752776
Compare
60006b1
to
f0c8baf
Compare
f0c8baf
to
3cde37d
Compare
3cde37d
to
1a3fd95
Compare
87e353d
to
50c4977
Compare
5438b70
to
aff49d2
Compare
272bc14
to
7d032c9
Compare
7d032c9
to
c6c19f2
Compare
c6c19f2
to
0a38334
Compare
halfzebra
approved these changes
Sep 29, 2020
🎉 This PR is included in version 4.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.4.1
Release Notes
github/fetch
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:
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 aArrayBuffer
as per the specification. -- #816Request
andResponse
can now only be called vianew
(as constructors) as per the specification. -- #796Headers which are passed as a
Headers
object no longer have their names normalised as per the specification -- #798Refactor:
this
to stop warnings being emitted from Rollup. -- #815v3.2.0
Compare Source
Features:
Bug fixes:
new
- #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. -- #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. -- #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 intoBlob
s if the browser supportsArrayBuffers
-- #752Added compatibility for
fetch-mock
-- #736Making 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
Compare Source
Renovate configuration
📅 Schedule: "after 10pm every weekday,before 5am every weekday,every weekend" (UTC).
🚦 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 WhiteSource Renovate. View repository job log here.