Upgrade whatwg-fetch to version 3.0.0

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ whatwg-fetch (~2.0.3 → ~3.0.0) · Repo

Release Notes

3.0.0

• 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 omit → same-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.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 69 commits:

• Fetch 3.0.0
• Merge pull request #654 from github/flowtype
• Add DOMException to type definitions
• Add `.flow` files to npm package
• Add flow definitions
• Expand install & importing documentation
• Merge pull request #651 from github/body-unsupported-type
• Merge pull request #652 from github/karma-update
• Fix worker config
• Avoid running Chromium in CI
• Bring back `--no-sandbox` for Travis CI compatibility
• Prefer headless testing
• Match spec behavior re: unsupported body type
• Remove unnecessary test assertions
• Use karma-detect-browsers to make things simpler
• Skip test for `credentials` default on Safari
• Automatically test with Safari on macOS
• Update Karma to latest version
• Merge pull request #649 from github/contributor-covenant
• Fix code of conduct contact email
• Adopt Contributor Covenant Code of Conduct
• Merge pull request #640 from github/credentials-default
• Note the changing `credentials` default in Caveats
• Point out that the default for `credentials` has changed
• Change `credentials` default value: `omit` → `same-origin`
• Clarify that all modern browsers now implement fetch natively
• Merge pull request #626 from github/karma
• Install newer Firefox in hopes to avoid intermittent CI failures
• Avoid Node 6 deprecation warnings re: Buffer
• Rename `prepublish` step to `prepare`
• Remove xvfb since it's no longer necessary in CI
• Enable AbortController polyfill in web worker mode
• Tweak bullet styles
• Remove docs that are of little to no use
• Improve CONTRIBUTING documentation
• Configure eslint for node
• Have test output in CI be less noisy
• Skip iterable tests broken in Firefox <= 56
• Add `npm run karma` for easier testing
• Skip `response.formData()` test in native Safari/Edge
• Skip testing functionality that doesn't seem implemented in IE/Edge
• Fix abortable tests in Safari
• Only test native abortable functionality in browsers that implement it
• Remove PhantomJS artifacts from tests
• Load polyfills for testing older browsers
• Remove test that depends on specific abortcontroller-polyfill API
• Split header values with `, ` to match other browsers
• Nuke old testing setup
• Convert testing fetch under Web Workers to Karma
• Switch from PhantomJS to Karma + Chrome/Firefox for testing
• Merge pull request #592 from jamesplease/abort-polyfill
• Polish documentation for aborting requests
• Export DOMException for `instanceof` checks
• Scope abortcontroller to polyfill only
• Merge remote-tracking branch 'origin/master' into abort-polyfill
• Merge pull request #616 from jayphelps/umd
• Try testing with a newer Node version
• Merge remote-tracking branch 'origin/master' into umd
• Use new exports to clean up test suite preparation
• Quit testing CJS exports directly
• Build UMD dist file with Rollup
• Run test files through prettier
• Have tests pass eslint
• Switch from jshint to eslint
• Make `fetch.js` compatible with eslint
• Run prettier on source file
• Add exports to `fetch.js`
• Unwrap `fetch.js` to be a clean module file
• Distribute as UMD

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[pull-assistant]

Best reviewed: commit by commit

---

Optimal code review plan

     Update whatwg-fetch to version 3.0.0

Powered by Pull Assistant. Last update 68c57d6 ... 68c57d6. Read the comment docs.