Environment variables

Vite exposes only variables prefixed with VITE_ to client code via import.meta.env. Configuration lives in nifty_fifty_bank_nifty_ReactJS/.env.

Required variables

Variable	Example	Purpose
`VITE_APP_BASEURL`	`http://localhost:3005/api/`	Axios API base URL (must end with `/api/`)
`VITE_APP_SOCKET_URL`	`http://localhost:3005`	Socket.IO server origin (no path)

Used in:

Variable	Example	Purpose
`VITE_APP_VERSION`	`v9.3.0`	Display version (if referenced in UI)
`VITE_APP_EMAIL`	`admin@yopmail.com`	Pre-fill login email in dev
`VITE_APP_PASSWORD`	`Admin@123`	Pre-fill login password in dev

AuthLogin.tsx reads dev credentials:

initialValues={{
  email: import.meta.env.VITE_APP_EMAIL || '',
  password: import.meta.env.VITE_APP_PASSWORD || '',
}}

Never commit production passwords. VITE_* values are embedded in the client bundle and visible to anyone.

Variable	Example	Purpose
`PUBLIC_URL`	`http://localhost:3005/`	Asset public path
`GENERATE_SOURCEMAP`	`false`	Disable source maps in production builds

Environment	`VITE_APP_BASEURL`	`VITE_APP_SOCKET_URL`
Local	`http://localhost:3005/api/`	`http://localhost:3005`
Staging	`https://bnn50api.sapphiresolutions.in.net/api/`	`https://bnn50api.sapphiresolutions.in.net`
Production	Set per deployment	Same host as API

Backend must listen on the same origin/port as VITE_APP_SOCKET_URL for WebSocket upgrade (see ops/environment/backend).

src/vite-env.d.ts references Vite client types. Add explicit ImportMetaEnv entries if you want IDE autocomplete for custom keys.