chore: ignore tsbuildinfo files - #2225
Merged
Merged
Conversation
`tsc -p tsconfig.node.json` writes tsconfig.node.tsbuildinfo on every `npm run lint`, because that config sets "composite": true, which keeps incremental output even under --noEmit. The file was showing up as untracked after each local run.
felladrin
marked this pull request as ready for review
July 27, 2026 13:57
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
1 participant
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.
Description
Currently, every
npm run lintleavestsconfig.node.tsbuildinfobehind as an untracked file, sogit statusis dirty after a routine lint run and the artifact is one carelessgit addaway from being committed.It comes from
tsc -p tsconfig.node.json: that config sets"composite": true, which keeps incremental build output even under--noEmit. Ignoring the pattern is enough, and*.tsbuildinfoalso covers any other config that starts emitting one later.Nothing matching the pattern is tracked today, so no
git rm --cachedis needed.Type of Change
Checklist
npm run lintpassesnpm run test), with tests added where it made senseHow to test
rm -f tsconfig.node.tsbuildinfo && npm run lintgit statusshould be clean, andls tsconfig.node.tsbuildinfoshould still show the file (ignored, not gone).git check-ignore -v tsconfig.node.tsbuildinfoshould point at the new line.