Build fluency in the SolidJS meta-framework SolidStart.
0 / 5 completed
1 / 5
At standup, a dev wants a meta-framework for SolidJS with file-based routing and SSR. Which one fits?
SolidStart is the official meta-framework built on SolidJS, providing file-based routing, SSR, and data loading conventions tailored to Solid's fine-grained reactivity. It plays the analogous role Next.js plays for React. Choosing it keeps the app in the Solid ecosystem end to end.
2 / 5
During a design review, the team fetches route data on the server before rendering. Which SolidStart primitive fits?
SolidStart routes define data loading using a load function combined with createAsync, integrating with Solid's reactive primitives rather than a separate framework-specific data-fetching API. This keeps data fetching consistent with Solid's signal-based model. It differs from the Next.js-style exported functions.
3 / 5
In a code review, a dev writes a function that only runs on the server and is stripped from the client bundle. Which SolidStart feature is this?
SolidStart server functions, marked with a 'use server' directive, run exclusively on the server and are callable from client code as if local, with SolidStart handling the RPC boundary. The function body is excluded from the client bundle. This mirrors patterns seen in other full-stack frameworks but tailored to Solid's compiler.
4 / 5
An incident report shows a page briefly flashes unstyled content, then hydrates. What SolidStart rendering mode was likely in use?
The described flash-then-hydrate symptom is typical of SSR with hydration, where the server-rendered HTML is replaced/activated by client-side Solid once JS loads. Diagnosing hydration mismatches or slow hydration is a common SSR troubleshooting step. This is core to how SolidStart delivers interactive pages.
5 / 5
During a PR review, a teammate wants a route to prerender at build time instead of per-request. Which SolidStart capability supports this?
SolidStart supports prerendering routes at build time for pages that don't need per-request data, similar to static generation in other frameworks. This improves performance and reduces server load for content that rarely changes. It complements the SSR and server function capabilities for dynamic routes.