-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to node-fetch
3.0 final
#2434
Comments
I tried to look into this today: I'm not entirely sure if/how that trips up kits build, but its very odd. |
tried it with a local node-fetch where i added "module" and "exports", no luck. There is a strange import to "streams/web" in If someone has an idea whats causing that import, i'd be glad to hear it. |
It looks like they tried to pollyfill it: I'm not sure why that isn't working |
the code that tries it is in if (!globalThis.ReadableStream) {
try {
Object.assign(globalThis, require('stream/web'))
} catch (error) {
// TODO: Remove when only supporting node >= 16.5.0
Object.assign(globalThis, require('web-streams-polyfill/dist/ponyfill.es2018.js'))
}
} |
aaaand there is a bug report on fetch-blob already node-fetch/fetch-blob#117 |
I tried building in node16 in local and node14.x in vercel, still the same error for not finding stream. |
Describe the problem
we're on a beta version
Describe the proposed solution
I tried briefly in #2422, but ran into some issue. I'd love if someone were able to take a closer look and figure out what's going on
Alternatives considered
No response
Importance
nice to have
Additional Information
No response
The text was updated successfully, but these errors were encountered: