cloudflare
Upcoming major version upgrade
In support of #2267 , we will be upgrading the Typescript library to remove dependencies on node-fetch. We expect that this migration will result in breaking changes and a need to bump the major version of the library. We are currently anticipating that this will land in early May 2025.
cc: @cloudflare/sdk
This issue hasn't been updated in a while. If it's still reproducing, please comment to let us know. Thank you!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue hasn't been updated in a while. If it's still reproducing, please comment to let us know. Thank you!
This issue hasn't been updated in a while. If it's still reproducing, please comment to let us know. Thank you!
Supposedly this was not addressed in 5.0? https://github.com/cloudflare/cloudflare-typescript/issues/2673#issuecomment-3258888204
@IanVS No it was not. It's on our list, but the team's focus has been almost entirely consumed by Terraform for the past couple of quarters. cc: @KaydeeDee
This issue hasn't been updated in a while. If it's still reproducing, please comment to let us know. Thank you!
In the next major version, I recommend setting an engines.node version to at least >= 18 (but ideally a higher version). Changing this value becomes a breaking change from there on out, but it substantially limits your support matrix and allows you to make these kinds of dependency updates much more easily.
The globalThis.fetch API was added in Node 16.15.0 and hasnt been experimental since 18.0.0 (hence the suggestion).
All variants of Node.js "native" fetch is achieved by an embedded copy of node-fetch, so including it as a dependency is just doubling-up for users who are on a Node version released anytime after ~Oct 2021
