Update solid-start-v2 templates to @solidjs/router 1 and @solidjs/start 2 rc

[brenelz]

Version updates across all 15 solid-start-v2 templates:

• @solidjs/router ^1.0.0 (from ^0.16.2; with-solidbase from ^0.15.3)
• @solidjs/start ^2.0.0-rc.6 (from ^2.0.0-beta.0)
• solid-js ^1.9.14: start 2 rc depends on ^1.9.14, and the older ranges pinned in the lockfiles resolved to 1.9.11, which installed a second solid-js copy alongside it

No source changes were needed. Router 1.0.0 is API-identical to 0.16.3 apart from scrollRestoration typings, and start beta.0 -> rc.6 carries no breaking changes for app code.

with-solidbase needs two workspace tweaks:

• an overrides entry forcing @solidjs/router 1, since solidbase still depends on ^0.15.3 and two router instances break SSR
• esbuild added to the packageExtensions for solidbase, which imports it without declaring it; it used to be satisfied by a copy hoisted from @solidjs/start's dependencies, which start 2 rc no longer pulls in

Verification

Per template: pnpm install, vite build, serve .output/server/index.mjs, HTTP 200. All 15 build and serve.

• with-auth 302s to /login, which then serves 200
• with-vitest tests pass
• with-drizzle verified with better-sqlite3 built and drizzle-kit push
• with-prisma with prisma db push + generate
• with-authjs with the env vars from .env.example
• with-solidbase prerenders and serves both routes
• basic: client-side navigation and hydration checked in a browser

with-tanstack-router, which has 500'd at SSR since #262, now works: / and /about serve 200 in both vite dev and the production server, it hydrates, and client-side navigation works with a clean console. The likely cause is rc.2 restoring the routerLoad argument to createHandler, which primes custom routers before SSR — that matches the symptom, but the mechanism wasn't confirmed.

solid-start-v1 templates are untouched: they stay on @solidjs/start 1.3.2 and @solidjs/router 0.15.

🤖 Generated with Claude Code