Skip to content

Conversation

@snyk-bot
Copy link

@snyk-bot snyk-bot commented Oct 8, 2021

Snyk has created this PR to upgrade whatwg-fetch from 3.0.0 to 3.6.2.

merge advice
ℹ️ 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.


  • The recommended version is 12 versions ahead of your current version.
  • The recommended version was released 7 months ago, on 2021-02-27.
Release notes
Package name: whatwg-fetch
  • 3.6.2 - 2021-02-27
    No content.
  • 3.6.1 - 2021-02-18

    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

  • 3.6.0 - 2021-02-18

    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

  • 3.5.0 - 2020-11-06

    Added a work-around for projects which use core-js -- #748

  • 3.4.1 - 2020-09-07

    Republishing to ensure the dist/fetch.umd.js is up-to-date

  • 3.4.0 - 2020-08-07

    Use globalThis as the global object if it exists #822

  • 3.3.1 - 2020-08-04
    No content.
  • 3.3.0 - 2020-08-04

    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
  • 3.2.0 - 2020-07-09

    Features:

    • Add support for no-cache and no-store - #795

    Bug fixes:

    • 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 new - #796

    Refactor:

    • Refactor DOMException handling code to avoid redundant exceptions generation - #797
  • 3.1.1 - 2020-07-08

    Bug fix

    -- check if Content-Type header exists prior to examining the value #792

  • 3.1.0 - 2020-06-29
  • 3.0.1 - 2020-07-08
  • 3.0.0 - 2018-09-10
from whatwg-fetch GitHub release notes
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

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