React Vite Template

Minimal React application foundation extracted from omnific-frontend for Omnific-Tech projects. Product-specific branding, business logic, API contracts, authentication, service workers, and deployment settings are intentionally excluded.

Included

• React 19, TypeScript, and Vite
• Tailwind CSS v4
• React Router
• TanStack Query and devtools
• Axios API client
• Zustand persisted preferences store
• Luxon date parsing and formatting helpers
• Global toast notifications with a queue limit
• shadcn CLI configuration and reusable UI primitives: Accordion, Button, Dialog, Field, Input, Label, Select, Separator, Spinner, Table, Textarea, and Tooltip
• Reusable debounce and intersection-observer hooks
• ESLint and strict TypeScript settings
• Bun lockfile

Create a project

From GitHub, select Use this template, or run:

gh repo create Omnific-Tech/my-project \
  --private \
  --template Omnific-Tech/react-vite-template \
  --clone
cd my-project
bun install
cp .env.example .env.local
bun run dev

Then update name in package.json, page metadata in index.html, and the starter shell under src/.

Add more shadcn components through its CLI:

bunx shadcn@latest add checkbox

Environment

Variable	Required	Purpose
VITE_API_BASE_URL	No	Base URL used by src/lib/api.ts; empty means same-origin requests.

Only variables prefixed with VITE_ are exposed to browser code. Never put secrets in frontend environment files.

Commands

bun run dev
bun run lint
bun run typecheck
bun run build
bun run preview

Run lint, typecheck, and build before pushing changes.

Structure

src/
├── components/ui/  # Shared UI primitives
├── layouts/        # Route layouts
├── lib/            # API, query client, and utilities
├── pages/          # Route-level pages
└── routes/         # Router configuration

Add domain code only after generating a project from this template. Keep this repository limited to defaults useful across multiple products.

Deliberate boundary

This template does not preload charts, calendars, Markdown, WebSockets, authentication, analytics, or deployment adapters. Add those when a product needs them. This keeps generated apps generic and avoids unused runtime dependencies while preserving the shared foundation from omnific-frontend.