Closed
Description
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:
- Many users of Sentry had to update the package to a new version in order to fix the issue: Undici 6.7.0 changes to request headers breaking Sentry code getsentry/sentry-javascript#10936
- This user also had to move from the built-in
fetch
tonode-fetch
: https://x.com/timcarrphoto/status/1795445427149422911 - More issues are likely to surface in the next few days, as AWS Lambda just completed the rollout in the past few days
What 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 @mcollina
What alternatives have you considered?
No response
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
mcollina commentedon May 28, 2024
@marco-ippolito can you include #53034 in the upcoming v20 release?
QuiiBz commentedon Jun 19, 2024
Will be closed by #53486 once it's released - it bumps Undici to
6.17.0
, which includes the fix.Edit: no longer planed for next release: #53486 (comment)
mcollina commentedon Jul 22, 2024
This will be fixed by 20.16.0.
QuiiBz commentedon Jul 25, 2024
Closing as Undici was updated to 6.19.2 in Node.js 20.16.0. Thanks!