Closed himself65 closed 3 weeks ago
@himself65 / @sindresorhus this was the first search result for an error I saw when upgrading my application (which does not use this project) from node-16 to node-18.
I see that this project tries to use node-14, and I wonder whether @himself65 was using this with node >= 18 when encoutering this issue.
I don't have a solution for my upgrade yet but wanted to share what I know so far.
Update, the solution in my case was to stop importing abort-controller
from npm and use the built-in that I get as part of upgrading node-16 -> node-18.
I think this is a bug in the old nodejs 18 version, now it seems to be fixed
Closing due to upstream fixes.
Upstream: https://github.com/nodejs/undici/pull/1910