Skip to content

Update dependency fetch to v3#31

Merged
Jared-Sprague merged 1 commit into
masterfrom
renovate/fetch-3.x
Feb 21, 2021
Merged

Update dependency fetch to v3#31
Jared-Sprague merged 1 commit into
masterfrom
renovate/fetch-3.x

Conversation

@renovate

@renovate renovate Bot commented Feb 20, 2021

Copy link
Copy Markdown

WhiteSource Renovate

This PR contains the following updates:

Package Update Change
fetch major 2.0.4 -> 3.6.1

Release Notes

github/fetch

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 #​914

v3.6.0

Compare Source

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 undefined and be 'null' if set to null -- #​897 Thank you for the contribution @​tkrotoff

  • Represent non-stringified JSON request body as an [object Object] string -- #​881 Thank you for the contribution @​kettanaito

v3.5.0

Compare Source

Added a work-around for projects which use core-js -- #​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. -- #​814

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 a ArrayBuffer as per the specification. -- #​816

  • Request and Response can now only be called via new (as constructors) as per the specification. -- #​796

  • Headers which are passed as a Headers object no longer have their names normalised as per the specification -- #​798

Refactor:

  • Removed the top-level this to stop warnings being emitted from Rollup. -- #​815

v3.1.0

Compare Source

Documentation:

  • Added documentation on features of fetch which are not polyfilled. -- #​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. -- #​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 into Blobs if the browser supports ArrayBuffers -- #​752

  • Added compatibility for fetch-mock -- #​736

  • Making 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.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 omitsame-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.


Renovate 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, check this box

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

@renovate renovate Bot force-pushed the renovate/fetch-3.x branch from a850907 to 7890a48 Compare February 21, 2021 02:14
@Jared-Sprague Jared-Sprague merged commit 1b55be9 into master Feb 21, 2021
@renovate renovate Bot deleted the renovate/fetch-3.x branch February 21, 2021 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants