.gitignore for Remix

Remix build output directory and local environment files.

Quick presets

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

5 patterns · 190 B

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

# ---- Remix ----
# Remix
/build/
/public/build/
node_modules/
.env
.cache/

What this template ignores

Ignores Remix server build/ and client public/build/ directories, node_modules, and .env secrets.

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 goes in Remix build/?
build/ contains the compiled server bundle. public/build/ contains client-side assets. Both are generated by remix build and should not be committed.

Looking for something else? Browse all templates →