Repository navigation
Void Server Components RFC - #871
Draft
kossnocorp wants to merge 1 commit into
Draft
kossnocorp wants to merge 1 commit into
kossnocorp wants to merge 1 commit into
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://server-components-void-cloud.voidzero-docs.workers.dev (commit 469aab0)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
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
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 is a follow-up for the discussion with @cpojer in #843. It also overlaps with #731 by @yusukebe that implements Hono JSX adapter but takes different direction.
It is a proposal to add built-in Void Server Components that would allow exporting a JSX component from
pages/**/*.server.tsx. The implementation is based onhono/jsxand enables server-only rendering without any client JS or even installing a view framework such as React or Vue.The body of the component becomes the loader:
But explicit loaders are also supported, so the API is consistent.
It also supports all the regular page features like
layout,prerender, CSS, error pages, etc.The idea is to provide a complete experience out-of-box and allow users build static pages before opting into using a heavier view framework.
The PR doesn't cover using islands and include client components yet. If we have an agreement on direction, we should definitely think it through how to approach it and provide great DX for people mixing server and client components without falling into the same traps as Next.js did.