Editor Settings vs Project Config
What you'll learn: How personal editor preferences differ from team-wide project configuration, and why both matter.
The Two Layers of Configuration
When working with linters and formatters, configuration happens in two distinct places:
- Editor settings – Personal preferences stored in your code editor (VS Code, WebStorm, etc.)
- Project config files – Shared files committed to Git (
.eslintrc,prettier.config.js, etc.)
Think of it like a restaurant: project config is the menu everyone agrees to serve, while editor settings are your personal kitchen tools and prep preferences.
Editor Settings: Your Personal Workspace
Editor settings control how your local environment behaves. Examples include:
- Whether format-on-save is enabled
- Font size and theme colors
- Keybindings for running ESLint
- Which extensions are installed
These live in files like .vscode/settings.json (for VS Code) or your global editor preferences. They're yours alone and typically not committed to version control.
Project Config: The Team Agreement
Project configuration files define what the code should look like. Examples include:
.eslintrcoreslint.config.js– which rules enforce code qualityprettier.config.js– how code gets formatted.prettierignore– which files to skip
These files are committed to Git so every team member gets the same linting rules and formatting behavior, regardless of their personal editor setup.
Why the Separation Matters
You might love format-on-save, but your teammate prefers manual formatting. That's fine—your editor settings differ. But you both must follow the same project rules when code is formatted, ensuring consistency in the repository.
Key Takeaway: Editor settings customize your personal workflow; project config files enforce shared standards. The former stays local, the latter lives in Git.