.gitignore for Node + Nuxt
.gitignore for Nuxt.js applications with full Node.js toolchain coverage.
Quick presets
Selected (2)
NodeNuxt
Your selections never leave your browser. Generation happens entirely client-side.
24 patterns · 493 B
# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator # Templates: Node, Nuxt # 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 # ---- Nuxt ---- # Nuxt.js .nuxt .output
Why use Node + Nuxt together?
Nuxt 3 uses Nitro as its server engine, which generates output in .output/ directory. Combined with the .nuxt/ build cache, these are the two most important Nuxt-specific ignores. The Node template covers the package manager side.
For Nuxt 2 projects, only .nuxt/ is relevant — .output/ is Nuxt 3+.
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 Node and Nuxt?
- Nuxt 3 uses Nitro as its server engine, which generates output in .output/ directory. Combined with the .nuxt/ build cache, these are the two most important Nuxt-specific ignores. The Node template covers the package manager side.
Looking for something else? Browse all templates →