cross-fetch

What's Changed

BREAKING CHANGES

• Dropped support for Node 10 and 12. (Note: cross-fetch will likely continue working on those versions, but specs tests are not running on those Node versions and no support will be provided if issues come up.)
• Please check implementation conflicts in the Fetch API tests.

FEATURES

• Added support for Node 18 and 20.
• Added support for Service and Cloudflare Workers (Fixes #69, #78, #148) by prioritizing native code over third-party implementation. Fetch API test suite now running against node-fetch, whatwg-fetch, native browser and native node fetch.
• Upgraded whatwg-fetch to 3.6.2. Please refer to whatwg-fetch release notes between 3.0.0 and 3.6.2 for features and bug fixes.
• fetch.ponyfill is set to true when custom implementation is used. This improves debuggability.

What's Changed

• Restored caret range to node-fetch version for automatic feature and fix updates.

Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.7...v3.1.8

What's Changed

• Updated node-fetch version to 2.6.12

Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.6...v3.1.7

What's Changed

• Updated node-fetch version to 2.6.11
• Added caret range to node-fetch version for automatic feature and fix updates.

Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.5...v3.1.6

What's Changed

• chore: updated node-fetch version to 2.6.7 by @dlafreniere in https://github.com/lquixada/cross-fetch/pull/124

New Contributors

• @dlafreniere made their first contribution in https://github.com/lquixada/cross-fetch/pull/124

Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.4...v3.1.5

🐞 fixed typescript errors.

🐞 fixed typescript compilation error causing #95, #101, #102.

🐞 added missing Headers interface augmentation from lib.dom.iterable.d.ts (#97)

🐞 fixed missing fetch api types from constructor signatures #96 (thanks @jstewmon)

⚡️ improved TypeScript support with own fetch API type definitions (thanks @jstewmon)
⚡️ set fetch.ponyfill to true when custom ponyfill implementation is used.
💡 set the same fetch API test suite to run against node-fetch, whatwg-fetch and native fetch.

⚡️ updated node-fetch to 2.6.1

⚡️ whatwg-fetch is not a prod dependency anymore (#63)
⚡️ updated all dev dependencies.

⚡️ upgraded node-fetch to 2.6.0.

🐞 fixed bug that crashed Safari 9 (#49).
⚡️ added VaporJS code to the project.

🐞 bugfix #35: fixed TypeScript failing on types when dom lib is not present.

🐞 bugfix #38: fixed the browser ponyfill stomping the global fetch function on React Native (thanks @msluther)

• major upgrade of whatwg-fetch to 3.0.0 (see breaking changes)
• minor upgrade of node-fetch to 2.3.0 (see changelog)
• comprehensive test coverage (from 16 specs to 72)
• dropped yarn in favor of npm for package management
• dropped npm in favor of make for tasks runner
• Now you can do import {fetch} from 'cross-fetch' on a browser bundle.
• For ponyfills, fetch.polyfill is now set to undefined instead of false.

🐞 bugfix #26: fixed TypeScript usage without esModuleInterop. (thanks @mattmccutchen)

🐞 bugfix #19: fixed typescript definitions (thanks @evert)

🐞 bugfix: fixed 'realFetch.call is not a function' when cross-fetch is bundled with webpack set to target node (@jamespedid, @alexvetter in #15)