Hover-prefetch fires real fetch requests for route loader chunks; those requests go through the same Playwright route handler that serves mocked modules. An in-flight prefetch landing after iframe teardown can hit the handler with a closed birpc channel, raising an unhandled rejection that exits the run with code 1 even when every individual test was green. Add `src/test-setup.ts` that sets `document.body.dataset.sveltekitPreloadData = 'off'` and wire it via `setupFiles` in both `vite.config.ts` (client project) and `vitest.client-coverage.config.ts` (Istanbul coverage config). Add `src/__meta__/browser-preload-disabled.svelte.test.ts` asserting the setup ran. Zero production impact. Issue #553 secondary trigger. Co-Authored-By: Claude Opus 4.7 (1M context) <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.