[Snyk] Upgrade whatwg-fetch from 3.0.0 to 3.6.2 #1
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.
Snyk has created this PR to upgrade whatwg-fetch from 3.0.0 to 3.6.2.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: whatwg-fetch
-
3.6.2 - 2021-02-27
-
3.6.1 - 2021-02-18
- Fixes a bug in v3.6.0 where the syntax used was not ES3 as it has used
- Fixes a bug in v3.6.0 where String.prototype.includes was used, which is not supported in IE 11
-
3.6.0 - 2021-02-18
-
-
-
-
3.5.0 - 2020-11-06
-
3.4.1 - 2020-09-07
-
3.4.0 - 2020-08-07
-
3.3.1 - 2020-08-04
-
3.3.0 - 2020-08-04
- Updated documentation for AbortController to recommend a polyfill which is spec-compliant and fully synchronous. -- #814
-
-
-
-
-
- Removed the top-level
-
3.2.0 - 2020-07-09
- Add support for no-cache and no-store - #795
- 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
- Refactor DOMException handling code to avoid redundant exceptions generation - #797
-
3.1.1 - 2020-07-08
-
3.1.0 - 2020-06-29
-
3.0.1 - 2020-07-08
-
3.0.0 - 2018-09-10
from whatwg-fetch GitHub release notesNo content.
Bug fixes:
constBoth 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
undefinedand be'null'if set tonull-- #897 Thank you for the contribution @ tkrotoffRepresent 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
No content.
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 aArrayBufferas per the specification. -- #816RequestandResponsecan now only be called vianew(as constructors) as per the specification. -- #796Headers which are passed as a
Headersobject no longer have their names normalised as per the specification -- #798Refactor:
thisto stop warnings being emitted from Rollup. -- #815Features:
Bug fixes:
new- #796Refactor:
Bug fix
-- check if Content-Type header exists prior to examining the value #792
Commit messages
Package name: whatwg-fetch
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs