Jake
f03f8a01b0
cargo fmt --check ✓ cargo clippy --workspace --all-targets -- -D warnings ✓ cargo test --workspace ✓ cargo nextest run --workspace ✓ 435/435 npm run check ✓ 0/0/5704 files npm test ✓ 13/13 (2 files) npm run test:browser ✓ 3/3 in Chromium npm run test:e2e ✓ 16/16 × 2 viewports npm run analyze ✓ reports/bundle-stats.html (1.7 MB) scripts/dogfood-rebrand-drill.sh ✓ 8/8 (sandbox) npm run guard:no-skeleton ✓ clean Two small Phase 8 corrections landed alongside the gate: vite.config.js: the jsdom suite was picking up `src/lib/ui/*.browser.test.ts`, which only works under the @vitest/browser-playwright provider. Added the browser-suffix glob to the jsdom suite's exclude list so the two runners stop double-running the same files. playwright.config.ts: bumped the global `expect.timeout` to 15 s. The cold first-compile of the Vite SPA tree was exceeding Playwright's default 5 s `toBeVisible` timeout on the 900x700 project on dogfood runs. The 1440x900 project (which runs second after a warm cache) never hit it. Phase 8 closes Phase-7 page migrations. Branch is ready for the finishing-a-development-branch handoff. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
76 lines
2.5 KiB
JavaScript
76 lines
2.5 KiB
JavaScript
// Using vitest/config rather than vite/config so one config surface drives
|
|
// `vite dev` / `vite build` AND `vitest run`. Vitest's defineConfig is a
|
|
// superset of Vite's — production builds ignore the `test` key.
|
|
import { defineConfig } from "vitest/config";
|
|
import { sveltekit } from "@sveltejs/kit/vite";
|
|
import tailwindcss from "@tailwindcss/vite";
|
|
import { visualizer } from "rollup-plugin-visualizer";
|
|
|
|
// @ts-expect-error process is a nodejs global
|
|
const host = process.env.TAURI_DEV_HOST;
|
|
// @ts-expect-error process is a nodejs global
|
|
const analyze = process.env.ANALYZE === "1";
|
|
|
|
// https://vite.dev/config/
|
|
export default defineConfig(async () => ({
|
|
plugins: [
|
|
sveltekit(),
|
|
tailwindcss(),
|
|
...(analyze
|
|
? [
|
|
visualizer({
|
|
filename: "reports/bundle-stats.html",
|
|
template: "treemap",
|
|
gzipSize: true,
|
|
brotliSize: true,
|
|
open: false,
|
|
}),
|
|
]
|
|
: []),
|
|
],
|
|
clearScreen: false,
|
|
server: {
|
|
port: 1420,
|
|
strictPort: true,
|
|
host: host || false,
|
|
hmr: host
|
|
? {
|
|
protocol: "ws",
|
|
host,
|
|
port: 1421,
|
|
}
|
|
: undefined,
|
|
watch: {
|
|
ignored: ["**/src-tauri/**"],
|
|
},
|
|
},
|
|
test: {
|
|
// jsdom gives storage-shim tests a real localStorage / DOMException /
|
|
// window surface rather than hand-rolled mocks. Tests can override
|
|
// per-file with `// @vitest-environment node` if they need to.
|
|
environment: "jsdom",
|
|
// Discover *.test.{ts,js} colocated next to source. Mirrors Rust's
|
|
// #[cfg(test)] sibling convention; no separate tests/ tree.
|
|
include: ["src/**/*.{test,spec}.{ts,js}"],
|
|
// Frontend tests must never reach into the Tauri backend; that surface
|
|
// is owned by `cargo test` in src-tauri/ and crates/. v0.2 browser-mode
|
|
// component tests live under *.browser.{test,spec}.{ts,js,svelte} and
|
|
// are run by `npm run test:browser` against vitest.browser.config.js —
|
|
// exclude them from this jsdom suite so they don't double-run.
|
|
exclude: [
|
|
"src-tauri/**",
|
|
"node_modules/**",
|
|
"build/**",
|
|
".svelte-kit/**",
|
|
"src/**/*.browser.{test,spec}.{ts,js,svelte}",
|
|
],
|
|
// Restore a clean global state between tests — vitest's restoreMocks
|
|
// unwinds vi.spyOn / vi.fn, clearMocks resets call history, and
|
|
// unstubAllGlobals undoes vi.stubGlobal. Prevents accidental leakage
|
|
// when tests share modules with module-level state.
|
|
restoreMocks: true,
|
|
clearMocks: true,
|
|
unstubAllGlobals: true,
|
|
},
|
|
}));
|