vitest.config.ts

import { defineConfig } from 'vitest/config'
import { fileURLToPath } from 'node:url'
import { resolve, dirname } from 'node:path'

const __dirname = dirname(fileURLToPath(import.meta.url))

const workspaceGlob = (pattern: string): string => (
  resolve(__dirname, pattern).replaceAll('\\', '/')
)

export const collectionWideTestInputs = [
  workspaceGlob('**/package.json'),
  workspaceGlob('**/{vitest,vite}.config.*'),
]

// Workspace packages are aliased directly to their `src/*.ts` entry points so
// vitest doesn't need them pre-built into `dist/`. Vite's import-analysis
// resolver ignores `resolve.conditions` for npm packages (the deps optimizer
// path), so a literal alias is the reliable mechanism. tsx for backend dev
// gets the same effect via NODE_OPTIONS=--conditions=source (see scripts/guardian/dev.ts).
const workspaceAliases = {
  '@': resolve(__dirname, './src'),
  '@traderalice/guardian-runtime': resolve(__dirname, './packages/guardian-runtime/src/index.ts'),
  '@traderalice/connector-protocol': resolve(__dirname, './packages/connector-protocol/src/index.ts'),
  '@traderalice/ibkr': resolve(__dirname, './packages/ibkr/src/index.ts'),
  '@traderalice/opentypebb': resolve(__dirname, './packages/opentypebb/src/index.ts'),
  '@traderalice/uta-protocol': resolve(__dirname, './packages/uta-protocol/src/index.ts'),
}

const uiAliases = {
  ...workspaceAliases,
  '@': resolve(__dirname, './ui/src'),
}

export default defineConfig({
  resolve: {
    alias: workspaceAliases,
  },
  test: {
    // Vitest's affected-test lane follows static imports, but collection-wide
    // inputs must invalidate every project. Vitest compares changed files as
    // absolute paths, so relative defaults do not match this workspace; keep
    // absolute, slash-normalized globs explicit for every platform.
    forceRerunTriggers: collectionWideTestInputs,
    // The Node suite includes installer, PTY, and Guardian specs that spawn
    // their own process trees. CPU-relative worker counts scale contention
    // back up on larger development hosts, while two workers still saturate a
    // two-core CI runner by running Node and jsdom work together. Keep local
    // runs bounded at two workers and serialize the hermetic CI gate so child
    // process and timer-driven lifecycle tests retain execution capacity.
    maxWorkers: process.env.CI ? 1 : 2,
    projects: [
      {
        resolve: {
          alias: workspaceAliases,
        },
        test: {
          name: 'node',
          environment: 'node',
          setupFiles: ['./vitest.setup.ts'],
          include: ['src/**/*.spec.*', 'packages/**/*.spec.*', 'services/**/*.spec.*', 'apps/**/*.spec.*', 'scripts/**/*.spec.*'],
          exclude: [
            '**/*.e2e.spec.*',
            '**/*.bbProvider.spec.*',
            '**/*.live.spec.*',
            '**/node_modules/**',
          ],
        },
      },
      {
        resolve: {
          alias: uiAliases,
        },
        test: {
          name: 'ui',
          environment: 'jsdom',
          execArgv: ['--no-experimental-webstorage'],
          setupFiles: ['./vitest.setup.ts'],
          include: ['ui/**/*.spec.*'],
        },
      },
    ],
  },
})