feat: add tsconfig.json + consider using "AI" for coding#792
Closed
Topfi wants to merge 1 commit intogarrytan:mainfrom
Closed
feat: add tsconfig.json + consider using "AI" for coding#792Topfi wants to merge 1 commit intogarrytan:mainfrom
tsconfig.json + consider using "AI" for coding#792Topfi wants to merge 1 commit intogarrytan:mainfrom
Conversation
Surface type errors and explicit-any lint violations. Does NOT fix any errors — just adds the tooling and CI gate. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

feat: add
tsconfig.json+ consider using "AI" for codingThe Problem
This is a TS project.
This is a 50k LOC TS project.
This is a 50k LOC TS project for LLM personas.
This is a 50k LOC TS project for LLM personas without a
tsconfig.json.This is a 50k LOC TS project for LLM personas without a
tsconfig.jsonthat has grown to hundreds ofany.Suggested Fix
Add a standard issue
tsconfig.json, lint to surface explicitanyand install the required deps. Adjust CI and resolve all that'll surface now.tsconfig.json{ "compilerOptions": { "lib": ["ESNext"], "target": "ESNext", "module": "Preserve", "moduleDetection": "force", "moduleResolution": "bundler", "allowImportingTsExtensions": true, "verbatimModuleSyntax": true, "types": ["bun"], "strict": true, "skipLibCheck": true, "noEmit": true, "noFallthroughCasesInSwitch": true, "noUncheckedIndexedAccess": true, "noImplicitOverride": true }, "include": [ "bin/**/*.ts", "browse/**/*.ts", "design/**/*.ts", "lib/**/*.ts", "scripts/**/*.ts", "test/**/*.ts" ], "exclude": [ "node_modules", "browse/dist", "design/dist", "supabase/functions" ] }eslint.config.jspackage.json(additions){ "scripts": { "typecheck": "tsc -p tsconfig.json --noEmit", "lint:ts": "eslint \"bin/**/*.ts\" \"browse/**/*.ts\" \"design/**/*.ts\" \"lib/**/*.ts\" \"scripts/**/*.ts\" \"test/**/*.ts\"" }, "devDependencies": { "typescript": "^6.0.0", "@types/bun": "latest", "eslint": "^10.0.0", "typescript-eslint": "^8.0.0", "@eslint/js": "^10.0.0" } }Suggestion
Consider using an LLM (sometimes overhypingly called "AI") in your workflow. Any modern LLM going back to the Opus 4.1 days would have advised you to utilise the typesafety or go for plain JS. I understand that using LLMs in coding can be a bit scary, but these tools can provide some very helpful output, if one doesn't overdo it with excessive prompts that bloat the context window and of course audits all code the model outputs in full. Reading code, especially if not written by yourself, can be daunting, but it is important if you want to start using LLMs, that you continue to do so. Who knows what other issues could go unnoticed otherwise. Being an experienced developer, I am sure you will prefer sticking with writing everything yourself though.
Severity
🤖 Generated with Claude Code