Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
import { defineConfig } from 'vitest/config';
import { fileURLToPath } from 'node:url';
import { applyRunnerSelection, vitestCaptureProjects, vitestCiPool, vitestRunnerSelection } from '../scripts/vitestCiPool.js';
import { bootstrapVitestTempRoot } from '../scripts/lib/vitestTempRoot.js';
import { VITEST_WATCH_OPTIONS } from '../scripts/lib/vitestWatch.js';
import { SERVER_TEST_EXCLUDE, SERVER_TEST_INCLUDE, browserOwnerExcludes } from '../scripts/lib/workspaceTests.js';
// `npm run test:fast` is the Windows-safe way to set the flag (a
// `VITEST_FAST=1 vitest` script is parsed as an executable name on cmd.exe).
if (process.env.npm_lifecycle_event === 'test:fast') {
process.env.VITEST_FAST = '1';
}
// Reimports reuse the enclosing run root; capture projects share its one owner.
const RUN_TEMP_ROOT = bootstrapVitestTempRoot();
// The suite REQUIRES NODE_ENV=test: it is what selects the file storage backend
// (memoryBackend.js and every store facade) so no suite talks to the real
// Postgres. Vitest only DEFAULTS NODE_ENV to 'test' when it is unset, and PortOS
// runs under PM2 with NODE_ENV=development — so any commit made from a
// PortOS-spawned shell fires .githooks/pre-commit -> 'npm test --prefix server'
// with NODE_ENV=development inherited, and hundreds of suites then aim at the
// developer's live database (#4554). Forcing it here, rather than prefixing the
// npm script, keeps every entry point correct — 'npm test --prefix server', a
// bare 'npx vitest run', an IDE runner, the git hook — and stays Windows-safe
// (cmd.exe parses 'NODE_ENV=test vitest' as an executable name, which is why
// VITEST_FAST is set here too).
process.env.NODE_ENV = 'test';
// Node's module compile cache (`NODE_COMPILE_CACHE` env, or a CLI calling
// `module.enableCompileCache()` on itself — recent npm/npx builds do) writes
// to `TMPDIR/node-compile-cache` on every invocation of the process that
// enables it. That directory used to turn up rarely in the run-scoped temp
// root above (#9051) with no single spawn helper's isolation provably
// covering every child that could inherit the run's TMPDIR — the cache is
// process-wide, not tied to one call site, so isolating call sites one at a
// time can't rule out the next one. Disabling it tree-wide removes the
// possibility outright: honored since Node v22.1, and this repo requires
// `^22.22.2 || ^24.15.0 || >=26.0.0` everywhere it runs (`package.json`
// engines), so every supported Node build respects it.
process.env.NODE_DISABLE_COMPILE_CACHE = '1';
// The CI runner's explicit selection (closure-related files, minus the ones
// the test memo already verified) arrives as a file, not as CLI selectors.
const runnerSelection = vitestRunnerSelection();
const config = defineConfig({
server: { watch: VITEST_WATCH_OPTIONS },
// Anchor to the config, even when --root or the caller cwd differs.
cacheDir: fileURLToPath(new URL('./.cache/vitest', import.meta.url)),
test: {
// Vitest 5's module cache is separate from Vite cacheDir; dependencies may be shared by worktrees.
fsModuleCachePath: fileURLToPath(new URL('./.cache/vitest/modules', import.meta.url)),
// Environment teardown also owns collection-only/skipped suite fixtures.
environment: fileURLToPath(new URL('./test/mediaRegistryEnvironment.js', import.meta.url)),
...vitestCiPool(),
// Workers get their own process.env — set it there as well as above.
env: {
NODE_ENV: 'test',
NODE_DISABLE_COMPILE_CACHE: '1',
TMPDIR: RUN_TEMP_ROOT,
TMP: RUN_TEMP_ROOT,
TEMP: RUN_TEMP_ROOT,
MAC_CHROMIUM_TMPDIR: RUN_TEMP_ROOT,
// Keeps spawned npm from writing debug logs into the developer's ~/.npm/_logs.
npm_config_logs_max: '0',
// The runner's selection is for THIS Vitest process only: a suite that
// spawns a nested Vitest on a fixture must not inherit it.
PORTOS_CI_TEST_SELECTION: '',
// Same for the memo store: a nested Vitest must point at its own directory or stay off.
PORTOS_TEST_MEMO_DIR: '',
},
// 30s on every platform (#7951). This WAS 10s off Windows, and the split
// has always been a fiction: the cost it budgets for is vitest's transform
// pipeline, which is slower on Windows but not cheap anywhere. Measured on
// macOS during a full `cd server && npm test`, against ~445ms for the same
// import in a quiet node process:
//
// services/cosToolRegistry.js 34.6s routes/imageGen.js 29.8s
// routes/settings.js 28.2s (then 0.5-1.0s per re-import)
//
// The whole run spends ~50% of tracked time on transform + import, so a
// test whose body is one `await import()` of a large graph is timed almost
// entirely on module loading. At 10s those files failed with ZERO failing
// assertions, in suites the change under test never touched, and the set
// moved run to run with machine load — which is how a habitually-red
// `npm test` stops being a gate anybody reads.
//
// The import-cost path was NOT ruled out — it was confirmed, and fixed
// where fixing it is correct: the heaviest unconditional loads are hoisted
// to file scope (module collection is not budgeted), pinned by the
// "heavy test imports stay hoisted" rows in `lib/importScoping.test.js`.
// This raise covers the tail that hoisting cannot reach — 269 test files
// hold an `await import()` inside a test or hook, and most are deliberate
// (a fresh instance after `vi.resetModules()`, a mock installed first, a
// branch-gated load), so moving them would change what they test. For that
// tail the flat 10s is a runner budget masquerading as an assertion.
testTimeout: 30000,
// hookTimeout tracks testTimeout, and must be set explicitly: vitest's 10s
// DEFAULT applies to hooks even when testTimeout has been raised. The
// image-gen route suites (clean/watermark/multipart) do a heavy dynamic
// `import('./imageGen.js')` plus sharp fixture encoding in beforeAll —
// comfortably under 10s when run alone, but over it on a contended worker
// during a full-suite run, where they failed with "Hook timed out in
// 10000ms" and ZERO failing assertions. That was first seen on Windows and
// read as a Windows quirk; #7951 measured the same failure on macOS, which
// is why this no longer branches on platform.
hookTimeout: 30000,
// Print worker console output directly instead of forwarding it to the main
// thread over RPC. This codebase logs heavily from fire-and-forget callbacks
// (the documented `.catch(() => console.log(...))` pattern, PTY/timer hooks,
// periodic sync/sweep loops) — a log can resolve AFTER its test returns, and
// when that late log raced vitest's worker teardown the run failed with
// "EnvironmentTeardownError: Closing rpc while onUserConsoleLog was pending"
// (all assertions passing). Bypassing the RPC console-intercept removes that
// path entirely. Tests that assert on console use vi.spyOn (unaffected).
disableConsoleIntercept: true,
// The client owns its own test runner (`client/vitest.config.js`, jsdom,
// `cd client && npm test`) which already covers every `client/src/**` test
// — including the pure helper tests (e.g. normalize.js sidecar resolution).
// So this server runner covers only server, scripts/migrations, and lib
// tests; it intentionally does NOT glob the client tree (its default node
// environment has no DOM, so DOM-dependent client tests would fail here).
// The scripts/migrations glob lets each one-shot migration be verified
// against synthetic fixtures.
// The standalone autofixer package ships pure, node-builtin-only helpers
// (sandbox.js isolation/promotion primitives) whose adversarial tests run
// under this node runner. docs/deps-doc.test.js guards DEPS.md against
// dependency drift; it lives next to the document it checks rather than
// in server/. The globs are shared with the CI runner, which enumerates
// the same set before Vitest starts (scripts/lib/workspaceTests.js).
include: [...SERVER_TEST_INCLUDE],
// The slashdo submodule ships its own node:test suites; vitest can't
// parse them and the broad `../lib/**` glob would otherwise pick them up
// as "no test suite found" failures that break --bail=1 CI runs.
// DB-backed suites run only in `vitest.config.db.js`, against portos_test.
// Keeping them in this file made ordinary Linux and Windows jobs import 29
// files solely to skip their 275 assertions when no test DB was configured.
// The DB job is the authoritative runner, so excluding the same canonical
// list here removes duplicate setup without reducing coverage.
//
// Heavy disk/git/Sharp integration suites. `npm run test:fast`
// (VITEST_FAST=1) drops them so a unit-only loop stays cheap; `npm test`
// and CI keep the full run. The git-guard files are NOT listed here —
// their real-git describes honor SKIP_HEAVY_INTEGRATION, and the leftover
// pure-logic cases still run under --fast.
exclude: [
...SERVER_TEST_EXCLUDE,
...browserOwnerExcludes(),
...(process.env.VITEST_FAST ? [
'services/worktreeReap.test.js',
'services/sprites/atlas.test.js',
'services/sprites/walk.test.js',
'lib/gitTestRepo.test.js',
// Real-Chrome-and-ffmpeg gated renders (#9033): each spends minutes on
// headless capture/encode even when only their pure-logic cases would
// otherwise run under --fast.
'services/htmlComposition/index.test.js',
'services/musicVideo/compositionRender.test.js',
] : []),
],
coverage: {
provider: 'v8',
reporter: ['text', 'text-summary', 'html'],
reportsDirectory: './coverage',
include: ['lib/**/*.js', 'routes/**/*.js', 'services/**/*.js'],
exclude: [
'**/*.test.js',
'**/index.js',
'**/cos-runner/**'
],
thresholds: {
lines: 30,
functions: 30,
branches: 30,
statements: 30
}
},
// Vitest 5 clears mock call history before every test by default
// (`clearMocks`, which was false through vitest 4). PortOS ACCEPTS that
// default rather than pinning it back: it is per-test isolation, not a
// behavior change to production code, and both suites are green under it.
// Note what it does and does not do — it calls `.mockClear()`, so
// `mock.calls` resets while an implementation set by a `vi.mock` factory,
// a `beforeAll`, or `mockReturnValue` SURVIVES into the next test. The
// consequence worth knowing: an `expect(fn).not.toHaveBeenCalled()` now
// proves only that the CURRENT test did not call it, never that no earlier
// test in the file did. Assert a cross-test claim inside the test that
// makes it.
//
// Vitest APIs (`vi`, `describe`, `afterEach`, …) are NOT injected as
// globals: every suite imports what it uses from 'vitest'. A file leaning
// on injected globals passed here but threw `vi is not defined` whenever it
// ran outside this config — e.g. `vitest run server/…` from the repo root,
// where no config applies (#9049). Off, a missing import fails in every run.
globals: false,
// Global setup: mocks getPeers → [] so test-created records never fan out
// to live sync peers. Per-suite vi.mock('./instances.js', …) overrides win.
setupFiles: ['./vitest.setup.js'],
// Runs once in the main process, before any worker starts and again once
// after the whole run finishes (unlike setupFiles, which runs per test
// file, per worker). Reports and removes whatever is left in
// RUN_TEMP_ROOT once every test has finished (#9032).
globalSetup: [fileURLToPath(new URL('../scripts/vitestTempRootSetup.js', import.meta.url))],
}
});
// Both projects share the safety env, setup files and time budgets. The
// root globalSetup owns one temp root across BOTH groups; project teardown
// must not remove it while another group still needs it.
config.test = applyRunnerSelection(config.test, runnerSelection);
config.test.projects = vitestCaptureProjects(config.test, { cacheDir: config.cacheDir, selection: runnerSelection });
export default config;