SolidStart, the full-stack meta-framework built on the fine-grained reactive library SolidJS, has reached a stable 2.0 release, a ground-up modernization that swaps its Vinxi build layer for direct use of Vite's Environment API. Creator Ryan Carniato described it as "a complete modernization of SolidStart on Vite 8 for Solid 1.x," arriving after more than a year of work and 25 alpha, beta, and release candidate builds.
SolidStart v1 leaned on Vinxi to coordinate the separate client and server builds a full-stack framework needs, because Vite 5 lacked a first-class way to configure them. With Vite's Environment API now available, the team rebuilt the framework directly on Vite 8 and its Rolldown-powered toolchain, gaining better compatibility with plugins such as Tailwind CSS v4 and direct integration with deployment plugins for Nitro v3, Cloudflare, and Netlify. The release also reworks CSS handling so lazy-loaded component styles are server rendered without the flashes of unstyled content that affected v1.
For existing users the upgrade is mostly mechanical. SolidStart v2 requires Node.js 24 and Vite 8, and the most visible change is moving framework configuration out of app.config.ts and into vite.config.ts, alongside adjustments to package imports, environment types, server runtimes, and middleware that are detailed in the migration guide.
New projects can scaffold v2 directly:
npm create solid --start --v2
Days after shipping stable, SolidStart was effectively moved into maintenance mode, a decision tied to the concurrent Solid 2.0 RC. In that release the team folds server functions, the serving layer, and file-system routing into core and a router-neutral package, then declares that "Start mode replaces SolidStart:
A metaframework exists to fill the gaps in its framework. SolidStart's job was to provide what core couldn't. Over the 2.0 cycle, each of those capabilities moved home: server functions into core, the serving layer into start mode, file-system routing into a router-neutral package. What remained at the end of that process was a wrapper around things that no longer needed wrapping.
So instead of shipping a hollow 3.0, we're retiring it. Start mode replaces SolidStart.
On Hacker News, commenter agila90 called it "an interesting move,":
SolidStart 2.0 was just announced a week ago and immediately placed into maintenance mode. That's an interesting move.
I just hoped that announcement would be another blog post.
Carniato replied:
SolidStart 2.0 has a very important role of moving current projects into the future. Better tooling was key and it was that rewrite work that allowed me to hoist relevant parts into the core. Now every Solid project benefits from no FOUC in dev, preloading tag emission during SSR streaming etc...
I think this is inevitable collapse with AI. We want to look for our tools in a single place. It doesn't have to differentiate between React and Next when React is the one actually providing the features.
The team notes that v2 is already running in production apps such as the OpenCode Console.
SolidJS is an open-source, fine-grained reactive JavaScript library created by Ryan Carniato that compiles components to direct DOM updates without a virtual DOM. SolidStart is its official meta-framework, adding server-side rendering, streaming, server functions, and file-system routing on top.