New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add RSC and RCC for turbopack to benchmarks #2620
Conversation
RSC: whole page is a server component RCC: whole page is a client component add `app` directory to test app
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Ignored Deployments
|
@@ -29,6 +29,10 @@ pub trait Bundler { | |||
fn has_server_rendered_html(&self) -> bool { | |||
false | |||
} | |||
/// There is a hydration done event emitted by client side JavaScript | |||
fn has_interactivity(&self) -> bool { | |||
true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could change has_interactivity
and has_server_rendered_html
to return an enum.
enum InteractivityMode {
None,
HydrationDone,
}
impl InteractivityMode {
pub fn is_interactive(&self) -> bool {
match self { ... }
}
}
enum RenderMode {
Client,
Server,
}
// etc.
This will make the following code clearer to understand, without having to know the order of arguments to Turbopack::new
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll do
* fixup ropes * add RSC and RCC for turbopack to benchmarks RSC: whole page is a server component RCC: whole page is a client component add `app` directory to test app
* fixup ropes * add RSC and RCC for turbopack to benchmarks RSC: whole page is a server component RCC: whole page is a client component add `app` directory to test app
RSC: whole page is a server component
RCC: whole page is a client component
add
app
directory to test appThis also makes sure that app dir is tested as part of the benchmark tests