jaspr-pre-rendering-and-hydration

To set up Jaspr hydration safely, use dual entrypoints like main.server.dart and main.client.dart, and annotate only the topmost interactive component with @client. This separates server rendering from browser interactivity and prevents invalid platform imports.

Your @client component breaks because parameters must be fully serializable across the server-to-browser boundary. Ensure all data passed into hydrated client components are initialization fields that can safely serialize during static or server rendering.

To prevent browser APIs from running during Jaspr pre-rendering, enforce server-only and client-only library import constraints. This ensures browser interactivity code runs exclusively in the client while server-only code runs during pre-rendering.

Yes, you can fetch data asynchronously during Jaspr server-side rendering by using server-only async components. Fetch data during the build phase and pass the serializable results into hydrated client components as initializing parameters.

The best way to structure a Jaspr app for static site generation is defining dual entrypoint files in pubspec.yaml, applying @client only to the highest interactive component, and maintaining strict import safety for server-only and client-only libraries.