This project has no linter and does not want one, but `strict` says nothing about a binding that is simply never read — and that is the one kind of dead code a reader cannot tell apart from a deliberate seam. `tsc` already walks every file, so it may as well answer the question. Three had accumulated: an unread `type View` import in App, and a `useGameMeta()` resolver in Controls and YourOwn, both of which draw their colours from somewhere else — the game-order list has its own resolver, and YourOwn reads the reader's own records directly. None of them were wrong, they were just leftovers that read as intent. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
23 lines
598 B
JSON
23 lines
598 B
JSON
{
|
|
"compilerOptions": {
|
|
"lib": ["ESNext", "DOM"],
|
|
"target": "ESNext",
|
|
"module": "ESNext",
|
|
"moduleResolution": "bundler",
|
|
"types": ["bun-types"],
|
|
"allowImportingTsExtensions": true,
|
|
"noEmit": true,
|
|
"strict": true,
|
|
"noUncheckedIndexedAccess": true,
|
|
"noUnusedLocals": true,
|
|
"noUnusedParameters": true,
|
|
"noImplicitOverride": true,
|
|
"noFallthroughCasesInSwitch": true,
|
|
"exactOptionalPropertyTypes": true,
|
|
"skipLibCheck": true,
|
|
"jsx": "react-jsx",
|
|
"verbatimModuleSyntax": true
|
|
},
|
|
"include": ["src", "test", "scripts", "serve.ts"]
|
|
}
|