Move transport implementations to the @bufbuild/connect package #546
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.
This PR moves the actual logic of the gRPC, gRPC-web, and Connect transports to subpaths in @bufbuild/connect.
For example, @bufbuild/connect/protocol-connect exports
createTransport
now - a function that takes the common transport options, but also ahttpClient: UniversalClientFn
. Moving it there makes sense for consistency (the server-partcreateHandlerFactory
sits right next to it). But this move will also be helpful to slim down our public API, and to support other platforms.This also enables the
isolatedModules
tsconfig option for our packages (we've been using the example project as a canary so far, but it didn't give us good coverage).