gitignore Generator
Select the stacks in your project and get a clean, deduped .gitignore - no install, nothing leaves your browser.
Stacks
These are curated starting points, not exhaustive - review before committing.
.gitignore
30 patterns across 4 stacks
# Generated with FeatureFactory .gitignore generator # Node node_modules/ npm-debug.log* yarn-debug.log* yarn-error.log* pnpm-debug.log* .pnpm-store/ .npm/ *.tsbuildinfo coverage/ .nyc_output/ # Vue / Vite dist/ dist-ssr/ .vite/ *.local /public/build/ stats.html # macOS .DS_Store .AppleDouble .LSOverride ._* .Spotlight-V100 .Trashes .fseventsd # Environment files .env .env.* !.env.example .env.local .env.*.local *.pem secrets.json
Stop tracking the files that don't belong
A .gitignore is the first line of hygiene in any repository. It keeps dependency directories, build artifacts, editor settings, and - most importantly - secrets out of version control. Get it wrong and you leak an API key or bloat every clone with node_modules/; get it right and history stays lean and safe.
Most real projects mix several ecosystems: a Laravel API with a Vite frontend, a Python service on a macOS laptop opened in VS Code. Rather than copy-paste blocks and hunt for duplicates, pick your stacks above and this tool merges them, emitting each pattern exactly once with clear section comments.
Clean repos are the foundation of clean measurement. If you want the signal behind engineering metrics, DORA tracking, and AI code review, start with disciplined basics. Browse the rest of our free developer tools or read the conventional commits guide.
Frequently asked questions
.gitignore lists path patterns Git should never track - build output, dependency folders, secrets, and editor cruft. Keeping it accurate stops you from committing node_modules/, a leaked .env, or a stray .DS_Store into shared history.Measure what you ship
A clean repo is step one. FeatureFactory helps engineering teams plan, build, and measure AI web development - with outcomes you actually own.
Get early access