What problem does it solve? Wiring a Vite frontend to a Litestar backend requires coordinating dev-server proxying, HMR, manifest-based asset resolution, and type generation across two coupled config files, and any mismatch silently breaks HMR or production asset URLs. ## Core Features & Use Cases - Mode-based integration: Configure SPA, template, HTMX, Inertia hybrid, SSR, SSG, or external modes with a single ViteConfig and matching vite.config.ts contract. - HMR and asset helpers: Use Jinja helpers like vite(), vite_hmr(), and vite_static() to resolve dev-server URLs in development and hashed manifest assets in production. - End-to-end type generation: Generate routes.ts, schemas.ts, SDK clients, and Inertia page props from Litestar OpenAPI via TypeGenConfig and the litestar assets CLI. - Use Case: Build a React + TanStack Router SPA served by a Litestar JSON API, with hot module replacement in dev, hashed bundles plus manifest.json in production, and typed route/schema imports shared between backend and frontend. ## Quick Start Ask the AI to scaffold a Litestar app with VitePlugin in SPA mode, a matching vite.config.ts using litestar-vite-plugin, and type generation enabled.