.editorconfig Generator

.editorconfig Generator

Build a valid, spec-compliant .editorconfig file for your project without memorising property names or cross-checking values. Pick a preset for your language, tweak the global defaults, toggle a few per-language overrides, and copy the result straight into the root of your repository.

EditorConfig files keep indent styles, line endings, character sets, and trailing-whitespace rules consistent across every editor and IDE your team uses. A misspelled property name or a value outside the allowed set is silently ignored, so a generator that only emits supported keys is the safest way to avoid quiet drift between developers.

Nutzung

1. Wählen Sie einen Schnelle Voreinstellung that matches your primary language (JavaScript/TypeScript, Python, Go, PHP, Ruby, Web, or Mixed). The preset pre-fills every global default below.
2. Adjust the Global Defaults — indent style, indent size, tab width, end-of-line, charset, max line length, trim trailing whitespace, and insert final newline.
3. Tick any Language Overrides you need. Each toggle appends a properly-scoped section such as [*.py] oder [{Makefile,makefile,GNUmakefile}] with sensible per-language rules.
4. Copy the generated file or download it as .editorconfig and drop it into the root of your repository. EditorConfig plugins in VS Code, JetBrains IDEs, Vim, Sublime, and most other editors pick it up automatically.

Funktionen

• Language presets – JavaScript/TypeScript, Python, Go, PHP, Ruby, Web (HTML/CSS/JS), and a Mixed profile that covers typical polyglot repositories.
• Every standard global property – indent_style, indent_size, tab_width, end_of_line, charset, trim_trailing_whitespace, insert_final_newlinefest, und die optionale max_line_length.
• Scoped overrides – one-click toggles for Markdown, YAML, JSON, JS/TS, CSS, HTML/XML, Python, Go, PHP, Ruby, Makefile (tab indent enforced), and .bat/.cmd (CRLF enforced).
• Live-Vorschau – the file updates on every change, with copy-to-clipboard and one-click download buttons.
• Nur clientseitig – the form state never leaves your browser; nothing is uploaded, logged, or stored server-side.
• Always valid – each emitted property is restricted to the values accepted by the EditorConfig specification, so your file will not be quietly ignored.

Why EditorConfig?

Without a shared configuration, a single repository can end up with tabs in one file, four spaces in another, and CRLF line endings sneaking in from a Windows contributor. EditorConfig solves that by letting one file at the project root express the formatting contract every editor must follow, before any linter or formatter even runs.