Solid 2 support in SolidStart: current migration path and preview/release timeline?

[nicolas-geysse]

Hi SolidStart team,

Could you share the current plan and an indicative timeline for using Solid 2 in an existing SolidStart application?

We maintain Deposium, a production document/search/chat application using SolidStart, with SSR, authenticated API routes, server functions and SSE streaming. We have already migrated to SolidStart 2 and prepared an isolated Solid 2 pilot covering several UI components, document readers, authentication and data stores. Our application migration is currently paused while we wait for a supported integration path.

The published package metadata checked on October 13, 2026 is:

• solid-js: stable 1.9.17, next 2.0.0-rc.15.
• @solidjs/start: stable 2.0.6, depending on solid-js ^1.9.15, with @solidjs/router >=0.16.0 <2.0.0-0 as a peer dependency.
• Our production branch currently pins SolidStart 2.0.5 and Solid 1.9.15.

We read the ecosystem roadmap discussion, Solid 2 support issue #2175 and the earlier migration PR #2091, which is closed without being merged. The issue mentions a future SolidStart 3, and a later comment points to Solid 2's Vite plugin start mode.

For planning an existing production application's migration, could you clarify:

1. Is Solid 2 integration still planned through a future @solidjs/start release, potentially SolidStart 3, or is the Vite plugin's start mode now the recommended migration path?
2. Is there an active tracking issue, branch or milestone for that integration and its migration guide?
3. Is a preview likely in the coming weeks or months, or is there no target yet? An approximate window would help; we understand that a firm date may not be possible.
4. What would you recommend preparing now for an application relying on SSR, server functions, API routes and session middleware, while avoiding a custom SSR host or an unsupported dependency override?

We are interested in a preview as well as a stable release, provided the intended integration and migration path are documented. This would help us decide when to resume the application migration and requalify our pilot against the current Solid 2 RC.

Thanks for your work and any guidance on the current direction.

[lxsmnsyc]

1. As with the general knowledge, Solid 2.0 deprecates Start 2.0 because the whole feature set is now available in Solid 2.0. Just use @solidjs/vite-plugin with start: true. With the exception of Start Devtools which is now its own thing (the vite plugin README has a guide there). There won't be Start 3.0: once Solid 2.0 is released, Start 2.0 will go LTS support for maintenance only.
2. I think the features are 1:1 so the there won't be that much migration (except the things mentioned in point 1), but wait for the news.
3. Same as point 1.
4. Same as point 1.

[nicolas-geysse]

Thanks @lxsmnsyc for the clarification, and thanks to Ryan for pointing us to the migration guide during the livestream! It makes the intended path much clearer.

Our isolated pilot already uses the Vite plugin's start mode, so we can build on that work and requalify it against the current templates, rather than wait for a SolidStart 3 release.

Two small documentation suggestions from comparing the guide with our production application's needs:

1. The guide links to the fullstack template at cbbd8ba2, whose package.json uses Solid beta.32 and bundled local tarballs. The current template uses RC.17 and published packages. Could the pinned reference be refreshed, or the recommended version set clarified? We understand the tarballs are included; this is about choosing the intended baseline, not reporting a broken install.
2. A worked migration example for an existing encrypted or storage-backed session, alongside the Node entry's multiple-Set-Cookie and SSE disconnect handling, would be helpful. The guide already explains the boundaries clearly; an executable example would make regression checks easier for larger applications.

We'll keep our existing application running and migrate in isolated slices. If we encounter runtime issues, we'll bring minimal reproductions rather than assume they are framework bugs.

Thanks again for the guide and all the work on Solid 2!