[brenelz]

This adds Solid 2.0 (solid-js 2.0.0-rc.19) as its own framework entry next to SolidStart. CONTRIBUTING asks for an issue before adding a framework, so please treat this draft as the proposal: happy to move the discussion to an issue or close this if you'd rather not track an RC.

Why a separate entry

The tracked SolidStart (2.0.6) runs on solid-js 1.9, which is what latest installs today. Solid 2.0 does not use SolidStart. Its full-stack setup is @solidjs/vite-plugin plus filesystem-routing, which is what create-solid generates for its "Solid 2.0" project type. Replacing SolidStart would end its history, so this keeps both. The entry has focusedFramework: false while Solid 2.0 is a release candidate.

What changed

• packages/starter-solid: create-solid 0.12.0 with project type "Solid 2.0", the default basic template, TypeScript, SSR enabled, and no devtools. Enabling SSR adds ssr: true to the plugin options, writes server.js, and points start at it. The Solid packages are pinned to exact versions afterwards, and first-party-dependencies.json lists the solidjs-owned packages (eslint-plugin-solid is from solidjs-community, so it is left out). The prompts were read from create-solid 0.12.0's source and applied to solidjs/templates at 0045e64, because the CLI couldn't run interactively here. Re-running pnpm create solid with those answers should give the same files; please flag it if not.
• packages/app-solid: a port of app-solid-start with the same routes and data. It builds with the plugin's start.node server (dist/server/node.js) and sets serverFunctions: true so the 'use server' loaders stay on the server, as SolidStart does by default.
• stats-generator: a serve/solid.ts script and an in-process handleRequest handler, plus entries in the four runtime benchmark lists and ssr-load.test.ts.
• results: the framework and package enums and a solid entry in frameworks.ts.

results/solid/ is not included; it should come from the CI run. The docs page, logo mappings, methodology sections, README links, and dependabot group are left for a follow-up once that first run lands. That follow-up should also make compareVersionLabels in prepare-chart.ts sort a prerelease before its release, since plain localeCompare puts 2.0.0 before 2.0.0-rc.19.

Verification

• After rebasing onto main, pnpm format:check, pnpm lint, and pnpm type-check pass, and app-solid and starter-solid build.
• node --test src/*.test.ts in stats-generator passes (76 of 76), and validate-first-party-dependencies.ts passes.
• pnpm knip reports one duplicate export in packages/results/src/schemas.ts, which is already on main.
• The starter benchmarks run locally through the tracked-file copy: build, dev server, install, framework dependencies, Node engines, browser baseline, and core-js.
• The app benchmarks run locally: SSR request throughput, server-side rendered, client-side rendered, and verify-ssr-load.ts.

Known differences worth a look

On a local laptop run, Solid 2.0's dev time is much faster than SolidStart's, but it ships more client JavaScript (the Solid 2 runtime chunk is about 26 KB gzipped against 9.6 KB), and its HTTP SSR load test trails SolidStart on the link-heavy /server-side-rendered page. Most of that gap is per-link work in the router's server link state, which solidjs/solid-router#701 reduces. These are not Depot numbers, so CI's run is the one to compare.

Checklist

• If updating UI/UX components ensure you have added screenshots or a gif or video of the changes to the PR description (no UI changes)
• If this is a dependabot PR that bumps a metaframework version, ensure that all package versions in the package match the versions installed by the metaframework version being bumped (not applicable)
• If this is a dependabot PR that bumps a metaframework version in a starter-* package, ensure that the deps, and file content matches the output of the metaframeworks recommended starter/default project (not applicable)

🤖 Generated with Claude Code

[AlexanderKaran]

@brenelz Remove the depandobot I should remove those myself lol

[AlexanderKaran]

@brenelz Looks good few asks/questions:

1. Could you please remove the addition to the docs package in this PR. We like to add those once the first run is done
2. This version is "solid-js": "2.0.0-rc.19" when will the official release be? Just curious on this one thats all

I feel doing this as a seperate meta-framwork makes sense the next question is when do we drop solid start?

[brenelz]

As far as to when Solid 2.0 stable will be out I'm not sure. Im expecting in the next couple weeks