fix(elysia): use Node transport on Node runtimes - #25015
Draft
mikamikasuki wants to merge 1 commit into
Draft
mikamikasuki wants to merge 1 commit into
mikamikasuki wants to merge 1 commit into
Conversation
Co-Authored-By: GPT-6.1 Sol <codex@openai.com>
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Elysia on Node currently defaults to Bun's fetch transport, bypassing the Node transport's proxy and TLS configuration. Choose the default transport by runtime so Node uses
makeNodeTransport, while Bun keepsmakeFetchTransportand explicit transport overrides continue to work. Regression tests cover both runtime defaults.Fixes #24048
Validation: Elysia transport tests and the required repository format, build, lint, and test commands passed.