Parent: #743
Bug
The web TypeScript config enables incremental compilation, so a normal direct validation command writes apps/web/tsconfig.tsbuildinfo into the working tree:
node node_modules/typescript/bin/tsc --noEmit -p apps/web/tsconfig.json
The command succeeds, but git status --short apps/web/tsconfig.tsbuildinfo shows the generated build-info file as untracked because the root .gitignore does not ignore TypeScript incremental build-info artifacts.
Expected
- TypeScript build-info files are treated as generated artifacts.
- Running the web type-check command does not leave a visible untracked
apps/web/tsconfig.tsbuildinfo.
- Source and TypeScript config behavior stay unchanged.
Proposed fix
Add a scoped .gitignore pattern for TypeScript build-info files and verify that the same type-check command still passes while the generated artifact is ignored.
This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information.
Parent: #743
Bug
The web TypeScript config enables incremental compilation, so a normal direct validation command writes
apps/web/tsconfig.tsbuildinfointo the working tree:The command succeeds, but
git status --short apps/web/tsconfig.tsbuildinfoshows the generated build-info file as untracked because the root.gitignoredoes not ignore TypeScript incremental build-info artifacts.Expected
apps/web/tsconfig.tsbuildinfo.Proposed fix
Add a scoped
.gitignorepattern for TypeScript build-info files and verify that the same type-check command still passes while the generated artifact is ignored.This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information.