1
Fork 0
react-tailwind-starter/README.md
Leonardo Devai 60d4fdca60 Review and modernize all 42 projects to the updated standard
Pinned 2026 toolchains (Go 1.26, Rust 1.98/edition 2024, Python 3.14 + uv, Node 24,
Zig 0.16, NixOS 26.05), postgres 18 / mongo 8, lockfiles built from, non-root
runtimes, .dockerignore, per-project LICENSE, READMEs with the git.devai.io clone
line, checkout@v7 CI. Security fixes in the legacy Rust APIs (any-password login,
self-assigned admin, hard-coded JWT secret), JWT alg/exp/sub enforcement across the
blog series, safe markdown links in the frontends, and many smaller bugs — every
project was built, run and exercised end to end.

Adds scripts/publish.sh + a CI publish job that splits every folder into its own
repo at git.devai.io/templates/<folder>.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01128fhuZbgivaSJvtMf4s1G
2026-09-27 21:10:38 +02:00

46 lines
1.7 KiB
Markdown

# react-tailwind-starter
The quickest sane React start: Vite 8, React 19, TypeScript and Tailwind CSS v4.
No router, no state library, no component framework — a clean slate that builds
in seconds and hot-reloads instantly.
## Run
Get it: `git clone https://git.devai.io/templates/react-tailwind-starter.git`
docker compose up --build
Open http://localhost:8080 — the production build, served by nginx.
Hot-reload dev server (Node 24):
npm ci
npm run dev # http://localhost:5173
## How it works
Tailwind v4 is configured in CSS, not JavaScript. `src/index.css` is a single
`@import "tailwindcss";`, and the `@tailwindcss/vite` plugin finds the class names
in your source files. There is no `tailwind.config.js` and no PostCSS config — add
design tokens with an `@theme { … }` block in the same CSS file.
`npm run build` type-checks (`tsc --noEmit`) and then bundles into `dist/`.
## Layout
vite.config.ts React + Tailwind Vite plugins
src/index.css Tailwind entry point (add @theme tokens here)
src/App.tsx landing screen — replace and go
nginx.conf SPA fallback + long-lived caching for hashed /assets/
Dockerfile npm ci + vite build, served by unprivileged nginx
## Deploy
Push to your own GitHub repo and the shipped workflow
(`.github/workflows/ci.yml`) tests the compose stack, publishes the image to
GHCR, and — once you set the `DEPLOY_HOST` / `DEPLOY_USER` variables and
`DEPLOY_KEY` secret — deploys it to your server over ssh.
---
Part of [devai.io](https://devai.io) — UI starters: `react-tailwind-starter` and
[`react-shadcn-starter`](https://git.devai.io/templates/react-shadcn-starter).