anti
aa0b22aacb
Pre-this-commit, ~80 rgba() literals across 24 files were hardcoding alert-red, warn-amber, info-cyan, panel-dark, and white-text-with-alpha shades that bypassed the token cascade. Net effect in light mode: the .eml/SESSREC drawers, AttackerDetail verdict pills, MazeNET net-box headers, OPEN/REPLAY action buttons, threat-intel cards, and all the dim 'whitish' overlays stayed on their dark-mode hex values, producing the unreadable panels in the screenshots. Sweep maps each rgba colour family onto the existing token by alpha bucket — rgba(13,17,23,*) -> var(--panel), rgba(255,65,65,*) -> var(--alert)/-tint-10, rgba(255,170,0,*) and rgba(224,160,64,*) -> var(--warn)/-tint-10, rgba(0,200,255,*) -> var(--info)/-tint-10, rgba(255,255,255,*) -> var(--fg-N)/var(--matrix-tint-N) by alpha. VERDICT_TONE in AttackerDetail (MALICIOUS/SUSPICIOUS/BENIGN/ NO SIGNAL) was the worst offender — string literals '#ff4d4d'/'#ffae42'/'#5fd07a'/rgba(255,255,255,0.4) baked into inline JS styles. Now resolves at render time via var(--alert)/ var(--warn)/var(--ok)/var(--fg-4). New tokens in :root: - --bg-color (alias of --bg) — drawers used this name with #0d1117 fallback that fired in every browser because nothing defined --bg-color. Adding the alias makes drawers re-tone. - --info / --info-tint-10 / --info-tint-30 — REPLAY buttons and any future neutral-secondary use. - --ok — semantic alias for 'verified good' (matrix in dark, emerald in light) so BENIGN pills stay readable across themes. Login.css left intentionally — pre-auth surface, not themed.
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint 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 ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])