aea37250f4
All checks were successful
CI / Unit & Component Tests (pull_request) Successful in 3m33s
CI / OCR Service Tests (pull_request) Successful in 20s
CI / Backend Unit Tests (pull_request) Successful in 3m35s
CI / fail2ban Regex (pull_request) Successful in 43s
CI / Semgrep Security Scan (pull_request) Successful in 20s
CI / Compose Bucket Idempotency (pull_request) Successful in 1m0s
Smallest possible first step of issue #560. Adds a shared __mocks__/$app/navigation.ts exporting every nav function as vi.fn(), and switches one consumer (DocumentRow.svelte.spec.ts) from a per-spec factory to vi.mock('\$app/navigation') (no factory) to verify Vitest's __mocks__/ redirect resolves for SvelteKit virtual modules in browser-mode tests. CI is the gate: if the migrated spec passes alongside the 35 unchanged factory call sites, the same redirect pattern is applied across the remaining $app/navigation, $app/state, $app/forms and paraglide factories. Per ADR-012, eliminating factory mocks shrinks the birpc teardown-race surface; this commit is the first concrete cut. Refs #560. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sv
Everything you need to build a Svelte project, powered by sv.
Creating a project
If you're seeing this, you've probably already done this step. Congrats!
# create a new project in the current directory
npx sv create
# create a new project in my-app
npx sv create my-app
Developing
Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:
npm run dev
# or start the server and open the app in a new browser tab
npm run dev -- --open
Building
To create a production version of your app:
npm run build
You can preview the production build with npm run preview.
To deploy your app, you may need to install an adapter for your target environment.