@sbtools/ui-web

To share UI components between SSR pages and a client SPA dashboard, use a unified React package that provides SSR renderers alongside client components. This consolidates rendering logic and ensures consistent design tokens across both environments.

Maintaining consistent theming across server-rendered and client-side dashboards requires a shared design-tokens system applied to both SSR renderers and the SPA. This ensures visual uniformity without duplicating styling logic.

You can build a plugin-driven dashboard SPA using a Vite-based architecture that supports token-based theming and plugin integration hooks. This allows interactive exploration of migration tooling sections within the client application.

Yes, the shared UI library supports SSR renderers for various dashboard pages including MigrationAudit, Depgraph, Erd, FrontendUsage, MigrationStudio, and Logs. This enables direct HTML rendering for these specific views.

Yes, you can use this UI toolkit to reduce duplication across multiple Supabase plugin dashboards. It consolidates UI rendering and design tokens into a single reusable package, eliminating redundant component logic.

You need SSR renderers alongside an interactive SPA dashboard to generate static HTML pages for views like MigrationAudit and Logs. This provides faster initial page loads and server-side rendering for non-interactive content.