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 Docker + Node

.gitignore for Dockerized Node.js applications.

Quick presets

Selected (2)

DockerNode

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

Raw

24 patterns · 527 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Node, Docker
# 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

# ---- Docker ----
# Docker
**/.dockerignore
docker-compose.override.yml

Why use Docker + Node together?

Containerized Node.js projects are common in microservices and CI/CD pipelines. This combination ensures node_modules is ignored (even if it is mounted in Docker, it should not be in the repo), docker-compose.override.yml keeps local dev overrides separate, and .env files with container secrets stay out of version control.

Related combinations

docker-python docker-node-react

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 Docker and Node?: Containerized Node.js projects are common in microservices and CI/CD pipelines. This combination ensures node_modules is ignored (even if it is mounted in Docker, it should not be in the repo), docker-compose.override.yml keeps local dev overrides separate, and .env files with container secrets stay out of version control.

Looking for something else? Browse all templates →