SolidStart 2

Apply the Solid 1.9 and Node.js 24 prompts first. These additional rules target SolidStart 2 (@solidjs/start), its server functions, Solid Router integration, H3 request/session helpers, SSR, and deployment boundaries, and were checked against 2.0.4.

Version and build boundaries

• Use a maintained Node.js 24 patch for this runtime profile; SolidStart 2.0.4 requires Node.js >=24. Resolve Vite within ^8 || ^9 and, when using Solid Router, @solidjs/router within >=0.16.0 <2.0.0-0. Check a non-Node deployment plugin's runtime separately from the Node build requirement.
• Keep every bundled or deployed seroval and seroval-plugins copy, including the one solid-js uses for hydration, on Seroval's newest release, and check them with npm ls seroval seroval-plugins after each upgrade. Seroval supports only its newest release and publishes each advisory about a month after the release that fixes it, and published Seroval advisories can be missing from the data npm audit and OSV read, so a clean audit says little here. SolidStart's caret range can stay at an old release in an old lockfile until npm update seroval seroval-plugins refreshes it; solid-js declares a tilde range that stays on one Seroval minor, so add an overrides entry when that range can't reach the newest release. Validate any override with its callers and rebuild both server and browser output; JSON mode and request-size limits don't replace a deserializer fix.
• Configure solidStart() from @solidjs/start/config in vite.config.ts with one deployment plugin. For Nitro v3, use