mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
44 lines
2.2 KiB
JavaScript
44 lines
2.2 KiB
JavaScript
module.exports = {
|
|
transform: {
|
|
'^.+\\.(t|j)s$': [
|
|
'ts-jest',
|
|
{
|
|
tsconfig: './tsconfig.test.json',
|
|
},
|
|
],
|
|
},
|
|
testEnvironment: 'node',
|
|
// Emit JUnit XML for Trunk flaky-test detection only when JEST_JUNIT_OUTPUT_DIR is set.
|
|
reporters: process.env.JEST_JUNIT_OUTPUT_DIR ? ['default', 'jest-junit'] : ['default'],
|
|
clearMocks: true,
|
|
coverageProvider: 'v8',
|
|
setupFiles: ['./jest.setup-env.ts'],
|
|
// jest.quarantine.ts first so it wraps the describe/it/test globals before any test file declares tests.
|
|
setupFilesAfterEnv: ['../frontend/jest.quarantine.ts', './jest.setup.ts'],
|
|
testMatch: ['<rootDir>/tests/**/*.test.ts', '<rootDir>/src/**/*.test.ts'],
|
|
testTimeout: 60000,
|
|
// The image-scrub sidecar is a standalone package with its own jest run; keep the plugin-server suite out of it.
|
|
modulePathIgnorePatterns: [
|
|
'<rootDir>/.tmp/',
|
|
'<rootDir>/src/ingestion/pipelines/sessionreplay/ml-mirror-image-scrub-sidecar/',
|
|
],
|
|
// `dev/` folders hold dev-only benchmarks/scripts, never CI tests. Anchored to rootDir:
|
|
// an unanchored '/dev/' also matches checkout paths like ~/dev/insights and ignores every test.
|
|
testPathIgnorePatterns: ['/node_modules/', '<rootDir>/(src|tests)(/.*)?/dev/'],
|
|
|
|
// NOTE: This should be kept in sync with tsconfig.json
|
|
moduleNameMapper: {
|
|
// `~/...` -> src/, `~/tests/...` -> tests/. The `.js`-suffixed variants come first to strip the
|
|
// nodenext extension: the production tsconfig is module: nodenext, which forces import()
|
|
// specifiers to carry `.js` (TS2835/TS2307), so ts-jest emits e.g. `~/foo.js` while only a
|
|
// `.ts` exists on disk. Jest only strips `.js` from *relative* specifiers (last rule), not from
|
|
// `~/` aliases — without these, an alias would resolve to a non-existent `src/foo.js`.
|
|
'^~/tests/(.*)\\.js$': '<rootDir>/tests/$1',
|
|
'^~/tests/(.*)$': '<rootDir>/tests/$1',
|
|
'^~/(.*)\\.js$': '<rootDir>/src/$1',
|
|
'^~/(.*)$': '<rootDir>/src/$1',
|
|
// Strip .js from relative imports so Jest resolves to the .ts source.
|
|
'^(\\.{1,2}/.*)\\.js$': '$1',
|
|
},
|
|
}
|