minsky/tsconfig.json at main · edobry/minsky · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
{
  "compilerOptions": {
    // Environment setup & latest features
    "lib": ["ESNext", "DOM"],
    "target": "ES2022",
    "module": "esnext",
    "moduleDetection": "force",
    "jsx": "react-jsx",
    "allowJs": true,
    "allowImportingTsExtensions": true,

    // Bundler mode
    "moduleResolution": "bundler",
    "verbatimModuleSyntax": false,
    "noEmit": true,

    // Best practices
    "strict": true,
    "skipLibCheck": true,
    "noFallthroughCasesInSwitch": true,
    "noUncheckedIndexedAccess": true,

    // Some stricter flags (disabled by default)
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "noPropertyAccessFromIndexSignature": false,

    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,

    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "outDir": "dist",
    "declaration": true,
    "sourceMap": true,
    "resolveJsonModule": true,
    "rootDir": ".",
    "typeRoots": ["./node_modules/@types", "./types"],
    "noImplicitAny": false,
    "types": ["bun"]
  },
  "include": [
    "src",
    "types",
    "tests",
    ".eslintrc.cjs",
    ".prettierrc.cjs",
    // mt#3817: nothing IMPORTS these, so import-reachability never pulled them
    // into a program and no project's `include` claimed them either. They are
    // application/deploy code, not build tooling, so they belong to the root
    // project rather than tsconfig.scripts.json:
    //   - services/*/deploy.config.ts is the deploy surface the mt#2353 merge
    //     gate fires on; each only imports @minsky/shared/deployment-config,
    //     so claiming them here does not drag service source into the program.
    //   - services/cockpit has its own tsconfig.json but no `typecheck` script
    //     and no CI step, so nothing ran it (one file). Folding it in here
    //     avoids a whole CI step for a single file.
    "services/*/deploy.config.ts",
    "services/cockpit/src"
  ],
  "exclude": [
    "node_modules",
    "dist",
    "build",
    // "scripts" is a DELIBERATE exclusion, not an oversight: it has its own
    // dedicated tsconfig.scripts.json (mirroring tsconfig.hooks.json's
    // pattern for .claude/hooks) and CI typecheck step, so a script file
    // reachable via import from something under "include" above isn't
    // double-checked here under a different (non-"bun","node") types config.
    // History: mt#3082 fixed 15 known errors and rejected adding this
    // dedicated project in its own scope (a probe surfaced ~180 latent
    // errors across ~43 files, including errors outside scripts/ entirely);
    // mt#3088 paid down that debt and added tsconfig.scripts.json.
    "scripts",
    "src/scripts",
    "src/cockpit/web",
    "tests/fixtures",
    "tests/integration/fixtures"
  ]
}

// Force TS Server to re-evaluate