Skip to content

Add Void runtime benchmarks and logo, update to 1.9.1 - #851

Merged
AlexanderKaran merged 6 commits into
e18e:mainfrom
yangshun:codex/add-void-runtime-benchmarks
Nov 17, 2026
Merged

AlexanderKaran merged 6 commits into
e18e:mainfrom
yangshun:codex/add-void-runtime-benchmarks

Conversation

@yangshun

@yangshun yangshun commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Adds app-void as the runtime follow-up to #844, following the invitation to submit the runtime setup before the docs follow-up. Also upgrades starter-void and the new app to Void and @void/react 1.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:

  • In-process SSR request-handler throughput, using the built production app's Fetch handler
  • Client-rendered and server-rendered paint and navigation tests
  • Initial-load resource downloads using the shared landing-page content and CSS
  • HTTP SSR load with plain anchors and with Void Link components

Server-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 = false and generate their UUID rows in the browser. The client-only detail page reads its selected ID with useParams(), 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:

  • Frozen installs, app/starter typechecks, runtime production build, and one normal cold/warm starter build and dev-server benchmark
  • All six actual runtime measurement commands; both HTTP load tests used the standard three full sweeps
  • Strict assembly of all six separate runtime artifacts, with every configured artifact required and no published results written
  • Chrome checks for SSR/CSR row counts, correct detail IDs, same-document navigation, absence of page errors, and the shared initial-load page styles
  • Chrome checks for the Void card logo in light and dark themes and the shared logo in Dev Time charts
  • Workspace typecheck, lint, formatting, docs build, full stats-generator test suite, and first-party manifest validation
  • Starter browser-baseline scan, with the Temporal exclusion still commented out; the raw scan remains limited (temporal) with 49 features

Local timing runs were validation only. CI retains the normal repetition counts and containerized HTTP load environment. I can maintain the Void integration after merge.

@yangshun yangshun changed the title Add Void runtime benchmarks and update to 1.9.1 Add Void runtime benchmarks and logo, update to 1.9.1 Nov 14, 2026
AlexanderKaran
AlexanderKaran previously approved these changes Nov 16, 2026
@AlexanderKaran

Copy link
Copy Markdown
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

@yangshun

Copy link
Copy Markdown
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.

@AlexanderKaran
AlexanderKaran merged commit f36bae1 into e18e:main Nov 17, 2026
106 checks passed
@AlexanderKaran

Copy link
Copy Markdown
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

@yangshun
yangshun deleted the codex/add-void-runtime-benchmarks branch November 17, 2026 05:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants