Christophe Vila
fe344867c0
LoginGate's initial session check swallowed every failure into the same "unauthenticated" branch, so a genuinely unreachable backend looked identical to a normal logged-out state -- the one screen in the app where "backend not here" showed no feedback at all, since every banner-migrated component only renders after authentication. api/client.ts's request() now throws a dedicated NetworkError (a distinct type, not just a distinguishable message) for a fetch() failure specifically, so LoginGate.tsx's catch can tell that apart from a real 401 via instanceof and show a banner before falling through to "unauthenticated" either way. Verified with a real headless-browser run against the dev server with no backend: the banner renders correctly and coexists with the existing ?auth_error= banner without conflict. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.