.gitignore for Angular + Node
.gitignore for Angular projects covering the full Angular CLI and Node.js toolchain.
Quick presets
Selected (2)
AngularNode
Your selections never leave your browser. Generation happens entirely client-side.
36 patterns · 649 B
# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator # Templates: Node, Angular # 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 # ---- Angular ---- # Angular tmp/ out-tsc/ .angular/ bazel-out/ npm-debug.log yarn-error.log .sass-cache/ /connect.lock /coverage /libpeerconnection.log testem.log /typings .DS_Store Thumbs.db
Why use Angular + Node together?
Every Angular project runs on Node.js since the Angular CLI is a Node tool. This combination gives you the full Angular build pipeline coverage plus Node.js toolchain patterns.
Related combinations
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 Angular and Node?
- Every Angular project runs on Node.js since the Angular CLI is a Node tool. This combination gives you the full Angular build pipeline coverage plus Node.js toolchain patterns.
Looking for something else? Browse all templates →