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 to stop tracking it without deleting the file locally.

.gitignore for Next.js + Node

.gitignore for Next.js applications with the full Node.js and npm/yarn toolchain.

Quick presets

Selected (2)

Next.jsNode

Your selections never leave your browser. Generation happens entirely client-side.

Raw

25 patterns · 509 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Node, Next.js
# 2026-04-20

# ---- Node ----
# Node
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
.pnpm-debug.log*
.npm
.yarn/cache
.yarn/unplugged
.yarn/build-state.yml
.yarn/install-state.gz
.pnp.*
lerna-debug.log*
.env
.env.local
.env.development.local
.env.test.local
.env.production.local
dist/
build/
.cache/
*.tsbuildinfo

# ---- Next.js ----
# Next.js
.next/
out/
.env*.local

Why use Next.js + Node together?

Next.js is built on Node.js, so every Next.js project needs both templates. The .next/ build cache is Next.js-specific and can grow large — it contains compiled pages, webpack chunks, and server-side rendering output. The out/ directory appears when using next export for static deployment.

Environment files deserve special attention in Next.js: .env.local, .env.development.local, .env.test.local, and .env.production.local are all local overrides that should never be committed. The base .env file (without secrets) is typically committed as documentation.

Related combinations

node-react macos-nextjs-node nextjs-node-visualstudiocode

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.
Why combine Next.js and Node?: Next.js is built on Node.js, so every Next.js project needs both templates. The .next/ build cache is Next.js-specific and can grow large — it contains compiled pages, webpack chunks, and server-side rendering output. The out/ directory appears when using next export for static deployment.

Looking for something else? Browse all templates →