Repository navigation
Add Void runtime benchmarks and logo, update to 1.9.1 - #851
Merged
AlexanderKaran merged 6 commits intoNov 17, 2026
Merged
Conversation
AlexanderKaran
previously approved these changes
Nov 16, 2026
Collaborator
|
@yangshun Looks good to me. I will merge this tomorrow and double-check benchmarks. I do have some more benchmarks coming; one will involve images. Would you be able to do a follow up PR adding the four routes needed? Well two if Void does not have an image component |
Contributor
Author
|
@AlexanderKaran for sure, happy to follow up. Void doesn't have image component yet but we'll be adding one soon. We can update the benchmarks then. |
Collaborator
|
@yangshun Thank you. If you take a look at the meta-frameworks they all have two new image routes using the default img tag. If you could replicate those for now. Then once you have an image component you can replicate the two other routes I am adding today |
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.
Adds
app-voidas the runtime follow-up to #844, following the invitation to submit the runtime setup before the docs follow-up. Also upgradesstarter-voidand the new app to Void and@void/react1.9.1, with independent lockfiles and an updated starter first-party dependency manifest. Direct dependencies are pinned to the latest compatible versions available when Void 1.9.1 was released.Adds Void's official logo from void.cloud, with the SVG copied unchanged into the site assets and registered in the shared logo mapping. The logo appears on the Void framework card and in charts. It has been checked on the card in light and dark themes and in the Dev Time charts.
The app uses React Pages with Void's Node target and retains the generated React Compiler setting and full client hydration. It registers all six runtime measurements:
LinkcomponentsServer-rendered tables use the shared 1,000-row UUID fixture and its zero-delay async loader on every request, without prerendering or caching rendered output. The paired load routes share identical loaders and table markup, differing only in link implementation. The throughput route renders the same rows without links. Client-rendered routes use
ssr = falseand generate their UUID rows in the browser. The client-only detail page reads its selected ID withuseParams(), without a server loader. Browser and HTTP tests launch the generated Node production server; the in-process benchmark imports the generated app directly.The integration follows Solid 2.0 (#709) for production-server and in-process-handler wiring, and Pracht (#439) for shared async SSR data, full hydration, browser-only CSR rows, client-side detail params, and paired plain-anchor/router-link routes. The initial-load page matches the shared React Router example from #735, apart from its relative CSS import.
The app README records the setup and route choices for review. The website methodology, framework detail page, and chart colors remain for the maintainer's docs follow-up. No local benchmark results are committed; CI will generate the results.
Validation with Node 24.22.1 and pnpm 11.1.1:
limited (temporal)with 49 featuresLocal timing runs were validation only. CI retains the normal repetition counts and containerized HTTP load environment. I can maintain the Void integration after merge.