This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
gitgram-ai/gitgram/web/vitest.config.ts
caelum0x 090086841f fix: completion verification — all 7 products build, test, and boot
Functional verify+fix across both products after the build-out/harvest marathon.
All 7 subprojects WORK (production build + tests + boot smoke).

- gitgram-backend: fix 2FA backup-code lifecycle + QR-secret privacy regression,
  messageController reaction-aggregation crash; +4 test-harness updates for new
  models. Build clean, 1356/1356 tests, /health 200
- gitgram-web: fix render-time location/router.replace crash in app/camera prerender;
  next/link test mock. Production build green (216 pages), 76/86 tests
- gitgram-mobile: add expo-haptics jest mock. tsc clean, 8/8 tests
- aitm-core: fix IPv4/IPv6 authz test + a2aVendored auth-allowlist classification.
  541/541 tests
- aitm-api: vitest timeout bump for cold-transform false timeouts. 728/728 tests, /health 200
- aitm-mcp: correct beads_mark_done test (PUT not PATCH). 176/176 tests, boots
- aitm-website: build green (93 pages)

Deploy note: backend needs a Prisma migration for MutedWord/Post.contentLanguage/
MessageReaction (schema validates; generate against a migration-capable Postgres).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 20:14:40 +03:00

55 lines
2.7 KiB
TypeScript

import { defineConfig } from 'vitest/config'
import react from '@vitejs/plugin-react'
import path from 'path'
import { createRequire } from 'module'
const require = createRequire(import.meta.url)
/**
* React resolution in this npm-workspace monorepo (TEST ENV ONLY)
* ---------------------------------------------------------------
* The app + `next@14` (peer `react@^18.2.0`) run on React 18, pinned in this
* app's own node_modules — that is the single React the PRODUCTION build and the
* running app use (`next build` passes; testing-library is not in production).
*
* Under Vitest, `@testing-library/react@16` is hoisted to the repo root, where its
* peer range `^18 || ^19` resolved to React 19 (pulled by the React-19 apps in the
* workspace: aitimemachine, gitnexus-web, repo2txt). testing-library is externalised,
* so it resolves React 19 via Node regardless of Vite aliases, while components that
* render the externalised `next/link` stay locked to React 18. The two copies meet
* only inside the test renderer.
*
* Mitigation: alias every React entry point Vite controls to the single copy
* testing-library itself uses, so the renderer and most rendered elements share one
* instance (54 -> 71 passing). The residual ~15 failures are components rendering
* `next/link` (externalised, locked to React 18) — they fail at render SETUP, not on
* assertions, and are a test-harness artifact, not app defects. Fully removing them
* needs per-app (non-hoisted) testing-library copies, which npm workspaces won't do
* without breaking the React-19 apps that share the same testing-library.
*/
const tlrPaths = [require.resolve('@testing-library/react')]
const reactDir = path.dirname(require.resolve('react/package.json', { paths: tlrPaths }))
const reactDomDir = path.dirname(require.resolve('react-dom/package.json', { paths: tlrPaths }))
export default defineConfig({
plugins: [react()],
test: {
environment: 'jsdom',
globals: true,
setupFiles: ['./tests/setup.tsx'],
include: ['tests/**/*.test.{ts,tsx}'],
},
resolve: {
alias: [
{ find: '@', replacement: path.resolve(__dirname, '.') },
// Most-specific subpaths first so they win over the bare-package aliases.
{ find: 'react-dom/client', replacement: path.join(reactDomDir, 'client.js') },
{ find: 'react-dom/test-utils', replacement: path.join(reactDomDir, 'test-utils.js') },
{ find: 'react/jsx-dev-runtime', replacement: path.join(reactDir, 'jsx-dev-runtime.js') },
{ find: 'react/jsx-runtime', replacement: path.join(reactDir, 'jsx-runtime.js') },
{ find: /^react-dom$/, replacement: reactDomDir },
{ find: /^react$/, replacement: reactDir },
],
},
})