Files
mission-control/tailwind.config.ts
teernisse 9cfd471d24 chore: configure build tooling and dependencies
Set up the foundational build configuration for Mission Control:

Frontend Build (Vite + TypeScript):
- package.json: React 19, TanStack Query, Zustand, Framer Motion
- tsconfig.json: Strict TypeScript with path aliases (@/)
- vite.config.ts: Tailored for Tauri (port 1420, ignores src-tauri)

Styling (Tailwind CSS):
- tailwind.config.ts: Custom surface color palette (zinc-900/800/700)
- postcss.config.js: Tailwind + autoprefixer pipeline
- tailwind.config.js: Generated config (superseded by .ts)

Code Quality:
- eslint.config.js: ESLint 9 flat config with TypeScript + React hooks
- .gitignore: Exclude node_modules, dist, coverage, test artifacts

This establishes the monorepo structure where:
- Frontend lives in src/ and builds to dist/
- Tauri backend lives in src-tauri/ with its own Cargo workspace
2026-02-25 17:01:05 -05:00

19 lines
393 B
TypeScript

import type { Config } from "tailwindcss";
export default {
content: ["./index.html", "./src/**/*.{js,ts,jsx,tsx}"],
darkMode: "class",
theme: {
extend: {
colors: {
surface: {
DEFAULT: "#18181b", // zinc-900
raised: "#27272a", // zinc-800
overlay: "#3f3f46", // zinc-700
},
},
},
},
plugins: [],
} satisfies Config;