Hugh KaznowskiandClaude Sonnet 5
ed0be9726f
"grey" and "dark" rendered identically apart from accent colour, so drop "grey" as a selectable colour scheme everywhere in the frontend (index.css, api.ts's ColorScheme type, the NavMenu picker, the downloadable BUILTIN_THEMES table) and keep "dark" as the single equivalent theme. Existing settings.json files saved with color_scheme: "grey" keep loading correctly: the backend ColorScheme enum aliases the legacy "grey" serde value onto Dark, so old configs transparently migrate to "dark" without any manual intervention. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XFUNZwCvz3kcod3352ZR2o
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the Oxlint configuration
If you are developing a production application, we recommend enabling type-aware lint rules by installing oxlint-tsgolint and editing .oxlintrc.json:
{
"$schema": "./node_modules/oxlint/configuration_schema.json",
"plugins": ["react", "typescript", "oxc"],
"options": {
"typeAware": true
},
"rules": {
"react/rules-of-hooks": "error",
"react/only-export-components": ["warn", { "allowConstantExport": true }]
}
}
See the Oxlint rules documentation for the full list of rules and categories.