[yangshun]

Add the official Void 1.8.0 React/Vite starter to the install, build, dev-server startup, dependency, and browser-baseline benchmarks. This implements the starter-first proposal in #683.

The starter was generated with:

pnpm dlx create-void@1.8.0 starter-void --toolchain vite --framework react --starter static --deploy none

It retains the generated welcome page, styles, assets, React Compiler setting, typed routes, and default Cloudflare build target. void and @void/react are pinned to the same exact version. The package has an independent lockfile, a first-party dependency manifest, and a standalone workspace. The added type-check script and ignored benchmark artifacts are documented in the methodology.

The build benchmark retains the complete Cloudflare build output for core-js scanning. An optional browserBuildOutputDir lets the baseline scanner use only the browser assets, preserving the existing default for other starters. Void also gets the existing Temporal exclusion used for starters that bundle optional serialization support without serializing Temporal values.

There is no runtime app in this PR. Results JSON is left to CI. The framework detail page, logos, and chart branding are deferred until the first published benchmark results, following the approach requested on #709; the methodology is updated here as required by the current contribution guide.

Validation with Node.js 24.22.1 and pnpm 11.1.1:

• Starter type check and production build
• Workspace type check, lint, formatting, and pnpm build:docs
• Stats-generator tests: 81 passing
• Actual tracked-file install, cold/warm build, and dev-server startup benchmarks, one repetition each for validation
• Framework/first-party dependency scans, Node engine scan, core-js scan, and browser-baseline scan
• First-party dependency manifest validation and strict CI artifact assembly with every configured artifact required, without writing published results

The pinned e18e analyzer produces valid dependency statistics but its publint step exits with an error because the generated private starter has no package version. The CI workflow already tolerates analyzer exit codes, and the resulting JSON passes the strict artifact validator.

I can maintain Void's integration after merge, including dependency upgrades, benchmark failures, and methodology updates.

[AlexanderKaran]

@yangshun Thank you so much for this will give it a good review tomorrow. Will there be a follow up for the app-void?

[yangshun]

@AlexanderKaran Definitely! Do you want me to submit a separate PR for it or combined into this? If separate, should I do it now, or after this PR has been merged?