Source: Apr 2026 conventions audit
Problem
`plugins/cc/` has no `tsconfig.json`. bun runs the .ts files directly without one, so it works — but:
- IDE/editors fall back to defaults that may not match bun's runtime
- `bunx tsc --noEmit` requires CLI flags every time
- Pre-commit hooks / CI can't easily enforce strict mode
- New contributors can't tell what TS dialect/options the project expects
Fix
`plugins/cc/tsconfig.json`:
```json
{
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "bundler",
"allowImportingTsExtensions": true,
"resolveJsonModule": true,
"skipLibCheck": true,
"strict": true,
"noUncheckedIndexedAccess": true,
"noImplicitOverride": true,
"exactOptionalPropertyTypes": true,
"types": ["bun-types"]
},
"include": ["**/*.ts"],
"exclude": ["node_modules", "dist"]
}
```
Acceptance criteria
Source: Apr 2026 conventions audit
Problem
`plugins/cc/` has no `tsconfig.json`. bun runs the .ts files directly without one, so it works — but:
Fix
`plugins/cc/tsconfig.json`:
```json
{
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "bundler",
"allowImportingTsExtensions": true,
"resolveJsonModule": true,
"skipLibCheck": true,
"strict": true,
"noUncheckedIndexedAccess": true,
"noImplicitOverride": true,
"exactOptionalPropertyTypes": true,
"types": ["bun-types"]
},
"include": ["**/*.ts"],
"exclude": ["node_modules", "dist"]
}
```
Acceptance criteria