From 1cf58b18e8a5e9d69725ad0f65c8c5448f17f50b Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Sun, 3 May 2026 00:13:04 -0400 Subject: [PATCH] ci(web): exclude #374-blocked tests from vitest module discovery MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit describe.skip inside the file doesn't help — the SvelteKit `notifiable_store is not a function` failure happens at module-load, before vitest evaluates describe blocks. Add the two paths to vitest's exclude list so the files aren't loaded at all. The skip markers stay inside the files as a triage signal for M7 #374. --- web/vitest.config.ts | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/web/vitest.config.ts b/web/vitest.config.ts index 291c6a92..b763a602 100644 --- a/web/vitest.config.ts +++ b/web/vitest.config.ts @@ -1,12 +1,25 @@ import { sveltekit } from '@sveltejs/kit/vite'; import { svelteTesting } from '@testing-library/svelte/vite'; -import { defineConfig } from 'vitest/config'; +import { configDefaults, defineConfig } from 'vitest/config'; export default defineConfig({ plugins: [sveltekit(), svelteTesting()], test: { environment: 'jsdom', include: ['src/**/*.test.ts', 'src/**/*.svelte.test.ts'], + // M7 #374: these two test files explode at module-load with + // `TypeError: notifiable_store is not a function` from SvelteKit's + // internal client.js — the import chain triggers SvelteKit's client + // runtime init in a way the dev-push vitest invocation can't satisfy. + // describe.skip inside the files doesn't help because vitest must + // load the file before it can see the describe block. Excluded here + // until the triage in #374 lands a real fix (probably a $app/paths + // mock in vitest.setup.ts). + exclude: [ + ...configDefaults.exclude, + 'src/routes/discover/discover.test.ts', + 'src/routes/requests/requests.test.ts' + ], setupFiles: ['./vitest.setup.ts'] } });