a5856e2f02
Some checks failed
CI / Unit & Component Tests (push) Failing after 2m59s
CI / OCR Service Tests (push) Successful in 30s
CI / Backend Unit Tests (push) Failing after 2m54s
CI / Unit & Component Tests (pull_request) Failing after 3m1s
CI / OCR Service Tests (pull_request) Successful in 29s
CI / Backend Unit Tests (pull_request) Failing after 2m54s
Addresses three blockers raised in PR #350 review (Felix, Sara, Tobias): 1. Replace all waitForTimeout(400) calls with waitForListbox() which uses waitForSelector('[role="listbox"]', { state: 'visible' }) — auto-waits for the debounce to resolve, faster on fast machines and reliable under CI. 2. Remove all conditional if (hasResults) / if (hasDropdown) wrappers. Tests now use unconditional expect(dropdown).toBeVisible() assertions so a missing-data condition causes an explicit failure instead of a silent green run. 3. Replace waitForSelector('[data-hydrated]') with waitForLoadState('networkidle') in getDocumentEditUrl — the data-hydrated attribute does not exist in the app markup and would cause a 30s timeout on every test. 4. Extract page: Page type import from @playwright/test and introduce waitForListbox(page: Page) helper to avoid repeating the selector pattern. 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.