-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Update Undici to backport a fix in Node.js 20.x #53186
Labels
feature request
Issues that request new features to be added to Node.js.
Comments
QuiiBz
added
the
feature request
Issues that request new features to be added to Node.js.
label
May 28, 2024
@marco-ippolito can you include #53034 in the upcoming v20 release? |
Merged
Will be closed by #53486 once it's released - it bumps Undici to Edit: no longer planed for next release: #53486 (comment) |
This will be fixed by 20.16.0. |
Closing as Undici was updated to 6.19.2 in Node.js 20.16.0. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the problem this feature will solve?
AWS Lambda recently completed a rollout from Node.js 20.12.x to Node.js 20.13.x, which includes this bug reported to Undici.
This impacts users using Node.js 20 in AWS Lambda, Netlify, Vercel, or any other service that uses AWS Lambda.
For example:
fetch
tonode-fetch
: https://x.com/timcarrphoto/status/1795445427149422911What is the feature you are proposing to solve the problem?
Update Undici to (at least) version
6.17.0
for the next Node.js 20 minor version, to includes the upstream fix. cc @mcollinaWhat alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: