v3 Roadmap

Note: v3 beta is now available on npm under the next tag

---

v3 Roadmap

General stuff

• BREAKING: Drop support for Node.js 4 and Node.js 6 (#489, #624)
• Update devDependencies (related to #489)
• When users clone(), automatically create streams with custom highWaterMark (#386, PR open: #671)
• Bundle TypeScript types (Support for TypeScript without need of installing @types/node-fetch package) (#669)
• Replace Rollup with Microbundle (#643)
• Introduce linting to the project (#303)
• Simplify Travis CI build matrix (related to #431) - Dropping support for Node.js 4 & 6 will help
• Response.statusText should not default (#578)
• Use w3c defined message for AbortError (#657)
• URL is not encoded as UTF-8 (#245)
• Deprecate timeout in favor of AbortController (#523)
• Data URI support (#659)
• Drop the optional dependency on encoding and move charset detection into a separate package. (In progress: Richienb/fetch-charset-detection (PR Open: #694))
• Drop existing blob implementation code and use fetch-blob as dependency instead (https://github.com/bitinn/node-fetch/issues/668#issuecomment-529175627)
• Fix stream piping (#309, PR open: #670)
• Fix stream resolving (#642, #665)
• Do not use constructor.name to check object (#667, PR open: #673)
• Properly forward request errors while piping response stream
• Convert Content-Encoding to lowercase (#661, PR open: #672)
• More tests for data URI (https://github.com/bitinn/node-fetch/issues/668#issuecomment-529175096)
• Drop credentials before redirection (#274)
• Modernise the code behind FetchError and AbortError (https://github.com/bitinn/node-fetch/issues/668#issuecomment-530845161)
• Propagate size and timeout to cloned response (#664)
• Replace the calls to url.parse and url.resolve with calls to new URL to use the new UTF-8 awareness and remove the utf8 package.
  • url.parse (https://github.com/node-fetch/node-fetch/pull/701)
  • url.resolve (https://github.com/bitinn/node-fetch/commit/e3cd4d22c3f1871fb41b17035ac83b47ad57fdf6)
• Document types of fetch errors more thoroughly (#549)
• Should update host if there’s a redirection (#570, PR Open: #596)
• High priority doesn’t correctly handle multiple content-type values (#783)

Additional:

• HTTP/2 support (#342, PR open: #796)
• Plugin/middleware system (https://github.com/bitinn/node-fetch/issues/668#issuecomment-533544800, PR open: #677)
• WebStream API support (#387) - needs more discussion and standard.
• Support trailers (#330) - trailer support has been removed (whatwg/fetch#772).
• Caching (#68) - would likely require opinionated implementation.
• Cookies (#94) - would likely require opinionated implementation.

Other

• Enable Dependabot to automatically update dependencies if they pass tests and are within an appropriate version range.
• A way to back/sponsor the project (#680)
• Create a final v2 release before releasing v3
• Update upgrade guide
• Release v1.x version of Richienb/fetch-charset-detection before release.
• Add this package to DefinitelyTyped/DefinitelyTyped/master/notNeededPackages.json since we now ship the typings.

---

cc @bitinn @jimmywarting @TimothyGu @jkantr @gr2m @Richienb

[gr2m]

I agree with @mariusa. v2 has been around for a long time and is stable. We can continue to accept bug fixes for v2 for a while.

With v3, we should drop support for Node < 12.8 and build node-fetch as native ES Module, without any transpilation to CJS, just make a clear break, similar to what Sindre laid out here: https://blog.sindresorhus.com/get-ready-for-esm-aa53530b3f77

[bitinn]

OK folks, 3.0.0-beta.1 is out, use npm install node-fetch@next to get it~

And 3.x branch is merged back into master now, we can use it from now on.

Someone should update the README to fix the badges and point people to v3 beta releases. Thx~