Why ignore node_modules?

node_modules is large and fully reproducible from package.json and the lockfile. Committing it bloats the repo and causes merge conflicts, so it is always ignored.

Should .env be in .gitignore?

Yes. .env files hold secrets like API keys and database URLs that must never reach version control. Commit a .env.example with placeholder values instead.

Do I commit package-lock.json?

Yes — the lockfile pins exact dependency versions and should be committed. This template only ignores node_modules, not the lockfile.

Where does the .gitignore file go?

Place it at the root of your repository as a file literally named .gitignore. Git applies its patterns to that directory and all subdirectories.

Does this cover build output?

Yes, when the build section is enabled it ignores common output folders like dist, build, .next, and .turbo. Toggle it off if you intentionally commit built assets.

.gitignore Builder for Node.js

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

A complete Node.js .gitignore

Starting a Node project means deciding what not to commit: dependencies, secrets, build artifacts, logs, and editor clutter. This builder generates a thorough .gitignore for Node, npm, and JavaScript projects, with each section toggleable so you only ship the patterns you actually need.

How it works

Git reads .gitignore from the repository root and applies each line as a pattern: a name matches files and folders anywhere below, a trailing slash matches directories only, and a leading slash anchors to the root. This builder assembles grouped sections — dependencies (node_modules/), environment files (.env, .env.local), build output (dist/, build/, .next/), logs (*.log, npm-debug.log*), coverage (coverage/, .nyc_output/), editor folders (.vscode/, .idea/), and OS files (.DS_Store, Thumbs.db). Toggling a section simply includes or omits its block in the live output.

Tips and example

Keep the lockfile (package-lock.json or yarn.lock) committed — it is not ignored here. A typical generated block includes:

# Dependencies
node_modules/

# Environment
.env
.env.local
.env.*.local

# Build output
dist/
build/
.next/
.turbo/

# Logs
*.log
npm-debug.log*

# OS files
.DS_Store
Thumbs.db

If you accidentally committed a file before adding it here, run git rm --cached <file> to stop tracking it while keeping it on disk.