23cbb6be22
Five tests in usePdfRenderer.svelte.test.ts called createPdfRenderer() without a libLoader, causing init() to dynamically import pdfjs-dist in the browser. Every dynamic import goes through Playwright's route handler, which calls resolveManualMock via birpc to check for mocks. If the RPC closes during teardown while one of these imports is in flight, the birpc race fires — even though pdfjs-dist was never explicitly vi.mock()-ed. Replace all bare createPdfRenderer() calls that invoke init() with createPdfRenderer(makeFakeLibLoader()), identical to the pattern already used in PdfViewer.svelte.test.ts. No real module loads, no route-handler calls, no birpc exposure. 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.