krishna_sales/vite.config.ts
ashwinkumaragurubaran 72ddba1c06 build: make artifact placement-portable for frontend releases
- vite base './' (relative asset refs) so one build serves any mount path
- index.html carries <!--BASE_HREF--> placeholder + ./config.js ref
- BASE_URL reads window.__RUNTIME_CONFIG__.VITE_ZINO_API_URL (placement-
  written) with a dev fallback

Required by frontgen 1600 assertBuildOutput + the dev->qa frontend
release model (target writes config.js from its own ZINO_API_URL).
2026-08-05 15:13:25 +05:30

13 lines
377 B
TypeScript

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import tailwindcss from '@tailwindcss/vite'
// Relative base so the built artifact is mount-path agnostic; the target
// frontgen writes the real <base href> into index.html at placement time.
const base = './'
export default defineConfig(() => ({
base,
plugins: [react(), tailwindcss()],
}));