feadf372a0
Production code referenced $lib/shared/services/confirm.svelte under two spellings — 4 files with the .js extension and one without. Standardise on the no-extension form to match Svelte 5 rune-module convention and the source file basename (confirm.svelte.ts). Why this matters: vitest browser mode's @vitest/browser-playwright resolves both spellings to the same module URL but registers a separate Playwright route per spelling. The route-cleanup logic only unregisters the latest, leaving an orphan that crashes the next session with "[birpc] rpc is closed, cannot call resolveManualMock". Fixed upstream in vitest PR #10267 (merged, not yet released). Normalising the spelling removes the trigger from our side. Refs: #553. Companion test-file changes follow in the next commit. 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.