.gitignore for Nuxt

Nuxt.js build artifacts, .nuxt cache directory, and static output.

Quick presets

Selected (1)
Nuxt
Your selections never leave your browser. Generation happens entirely client-side.
Raw

8 patterns · 226 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Nuxt
# 2026-04-20

# ---- Nuxt ----
# Nuxt.js
.nuxt
dist/
node_modules/
.output
.env
npm-debug.log*
yarn-debug.log*
yarn-error.log*

What this template ignores

Ignores the .nuxt build cache, .output/ (Nuxt 3 server output), static dist/, and local environment files.

Common additions

  • +.nitro/ — Nitro engine cache (Nuxt 3)

Commonly paired with

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.
What is .nuxt/?
.nuxt/ is the auto-generated build directory Nuxt creates when running dev or build. It contains compiled components, routing, and auto-imports. Never commit it.

Looking for something else? Browse all templates →