Remove Undici Dependency #395
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gavin-aguiar
approved these changes
Dec 2, 2025
auto-merge was automatically disabled
December 2, 2025 21:33
Repository rule violations found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Removed undici dependency completely
Replaced all undici usage with native Node.js fetch API (Request, Response, Headers, FormData, File).
Reason:
Headers is now a global type from Node.js's built-in fetch API (available in Node.js 18+). When we removed undici, we didn't need to change the Headers type reference because Node.js provides the same Headers class natively - it's automatically available in the global scope just like Request, Response, and FormData. The type definition comes from @types/node@^20.0.0 which includes all the native fetch API types, so TypeScript recognizes it without any imports.