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 adds basic support for Next.js via the new package
@bufbuild/connect-next
. It passed our tests, but still needs to be added to our test suite.The setup includes creating two files:
connect.ts
is where you register your RPCs:pages/api/[[..connect]].ts
is a Next.js catch-all API route:With that server running, you can make requests with any Connect or gRPC-Web client.
Note that Next.js serves all your RPCs with the
/api
prefix.Currently,
@bufbuild/connect-next
does not support the Vercel Edge runtime. It requires the Node.js server runtime, which is used by default when deploying to Vercel.