Ship a fast chat interface without dragging legacy assets into production.

This starter keeps Razor on the server, Vite in front of the asset pipeline, and Tailwind as the design layer. Development stays hot with HMR. Production stays deterministic with the Vite manifest.

ASP.NET Core docs Vite guide

Deployment profile

Production-safe assets

manifest.json

Frontend source /frontend

Dev experience HMR enabled

Static output /wwwroot/dist

Entry point

Legacy libs

100%

Tailwind UI

Development

Fast feedback loop

Run the backend with the HTTP launch profile and start Vite in frontend/ for live updates without rebuilding server assets.

Rendering

Razor stays in control

Views render on the server, while Vite injects the hashed JS and CSS bundle defined in the manifest for production requests.

Shipping

Static assets stay separate

The frontend output is ready to be served independently, which fits your plan for a dedicated Caddy image for static files.