crewli/apps/app/src/assets/styles/styles.scss at 62afbdedf8f3fb3063a3146ac7a9d60580ed7628 - crewli - Gitea: Git with a cup of tea

bert.hausmans/crewli

Files

bert.hausmans b7d814ad85 refactor(styles): move timetable tokens from .scss to .css for test-time loadability

Per Phase A finding A2 — `_timetable.scss` was functionally pure CSS:
only :root custom properties + @keyframes + one .tt-cascade-pulse class.
The only SCSS-specific syntax was `// line comments`. Zero $vars, @use,
@mixin, @function, nesting, or color functions.

Why move to .css: Vitest+jsdom can `import '@/styles/tokens/_timetable.css'`
directly so getComputedStyle() resolves var(--tt-…) in component tests
(needed for the upcoming PerformanceBlock visual-state assertions). SCSS
imports require Vite's SCSS plugin, which the vitest.config.ts intentionally
skips for unit-test speed.

Changes:
- `_timetable.scss` → `_timetable.css` (line comments converted to /* */
  block comments; everything else byte-identical)
- `assets/styles/styles.scss`: switch from `@use "@/styles/tokens/timetable"`
  to `@import "@/styles/tokens/_timetable.css"`
- Production `npm run build` passes (16s, no asset warnings)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-09 03:23:30 +02:00

6 lines

235 B

SCSS

Raw Blame History

 // Write your overrides
 // RFC-TIMETABLE v0.2 D21 — status palette + geometry custom properties.
 // Plain CSS so jsdom/vitest can also load it via `import '@/styles/tokens/_timetable.css'`.
 @import "@/styles/tokens/_timetable.css";