.gitignore for TypeScript
TypeScript compiled output and build info cache files.
Quick presets
Selected (1)
TypeScript
Your selections never leave your browser. Generation happens entirely client-side.
7 patterns · 216 B
# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator # Templates: TypeScript # 2026-04-20 # ---- TypeScript ---- # TypeScript *.js *.js.map *.d.ts !src/**/*.d.ts *.tsbuildinfo dist/ out/
What this template ignores
Ignores compiled JavaScript output, source maps, declaration files, TypeScript build info caches (*.tsbuildinfo), and output directories.
Common additions
- +
!src/**/*.d.ts — keep hand-written declaration files in src/
Commonly paired with
Frequently asked questions
- Do I need to commit .gitignore?
- Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
- How do I add custom patterns?
- Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
- How do I ignore a file that is already tracked?
- Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
- Should I ignore all .js files in a TypeScript project?
- Only if every .js file is compiled output. If your project mixes .ts and .js source files, be more specific (e.g., ignore dist/*.js or out/*.js).
Looking for something else? Browse all templates →