Updating node-fetch to v3

[larsgw]

From #29 (comment):

node-fetch 3 introduces a lot of breaking changes, the most problematic one being that the package has been converted to an ES module which makes it impossible to import synchronously.

My preferred workaround for this would be to only import node-fetch in the worker process, where asynchronous imports do not matter. This however requires writing a replacement implementation for the Response, Request and Header interfaces in the main process.

[jimmywarting]

Any consideration to switch to using undici or builtin fetch instead?

the npm package require NodeJS v16
it got added globally in NodeJS v18

node-fetch isn't going to get so much newer features as they are more or less taking over...

[larsgw]

That's a good point. I'll check when 16 is EOL.

[larsgw]

(That would be 2023-09-11)

[d07RiV]

Any update to this? Getting spammed with deprecation warnings now :(

[larsgw]

I'm swamped with other work this week, but I'm going to work on this next week.

[larsgw]

Update: I got started with this but there are a bunch of incompatibilities that I need to resolve. Right now SyncResponse is a subclass of the Response from node-fetch, but if I make it a subclass from Node's Response instead I basically need to rewrite the whole class.

[larsgw]

@d07RiV I've published a prerelease version (v0.6.0-0), could you try it out?

[d07RiV]

That works, thanks!