frontend-buildwww-vite

Multi-target Vite builds are configured by setting the BUILD_TYPE environment variable and running the corresponding npm script to produce dedicated output directories for app, htmx, and bootstrap assets.

TypeScript path aliasing in a Vite project is managed through centralized build configuration, ensuring correct module resolution and clear entry-point management for appPreload and appPostload outputs.

Yes, Vite works with Razor pages by generating built assets and manifests that are directly compatible with Razor page integration and shared library usage across the frontend project.

Manifest generation in a multi-target Vite build is needed to map original asset file names to their hashed, bundled versions, allowing backend frameworks to reference the correct output files.

Yes, you can use environment variables to select specific build outputs in Vite by assigning the target type to BUILD_TYPE, which triggers the appropriate npm script to build app, htmx, or bootstrap targets.

Multi-target Vite builds require strict adherence to specified configuration and output constraints via vite.config.js, meaning deviations in entry-point management or path aliasing may break the structured orchestration.