-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
Use only one copy of llhttp ? #44000
Copy link
Copy link
Closed as not planned
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.fetchIssues and PRs related to the Fetch API.Issues and PRs related to the Fetch API.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.fetchIssues and PRs related to the Fetch API.Issues and PRs related to the Fetch API.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
What is the problem this feature will solve?
Versions of Node using Undici (16, 18) are actually using two different copies of llhttp
What is the feature you are proposing to solve the problem?
Would it make sense to use llhttp wasm that is bundled in Undici, instead of recompiling it ?
What alternatives have you considered?
n/a it's a refactoring.