[Snyk] Upgrade whatwg-fetch from 3.0.0 to 3.1.0 #53
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.1.0.
ℹ️ 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
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
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 valueomit
→same-origin
to match the updated spec.fetch()
andnew Request()
now accept thesignal
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.
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