Switch to official YAML extension by default

docs/docs/configuration.md

@@ -1,14 +1,14 @@
 # Configuration <Badge type="tip" text="^0.8.0" />
 
-Herb uses a `.herb.yml` configuration file to customize how the tools behave in your project. This configuration is shared across all Herb tools including the linter, formatter, and language server.
+Herb uses a `.herb.yaml` configuration file to customize how the tools behave in your project. This configuration is shared across all Herb tools including the linter, formatter, and language server.
 
 ## Configuration File Location
 
-The configuration file should be placed in your project root as `.herb.yml`:
+The configuration file should be placed in your project root as `.herb.yaml`:
 
 ```
 your-project/
-├── .herb.yml    # Herb configuration
+├── .herb.yaml    # Herb configuration
 ├── Gemfile
 ├── app/
 └── ...
@@ -18,28 +18,28 @@ your-project/
 
 Configuration settings are applied in the following order (highest to lowest priority):
 
-1. **Project configuration** (`.herb.yml` file)
+1. **Project configuration** (`.herb.yaml` file)
 2. **Editor settings** (VS Code workspace/user settings)
 3. **Default settings**
 
 ## Basic Configuration
 
 ### Default Behavior (No Config File)
 
-If no `.herb.yml` file exists in your project:
+If no `.herb.yaml` file exists in your project:
 
 - **Language Server**: Uses built-in defaults and works out-of-the-box
 - **Linter**: Enabled with all rules (automatic exclusion of `parser-no-errors` in language server only)
 - **Formatter**: Disabled by default (experimental feature)
 - **Editor settings**: VS Code user/workspace settings are respected
 
 ::: tip Recommended for Projects
-If you're using Herb in a project with multiple developers, it's highly recommended to create a `.herb.yml` configuration file and commit it to your repository. This ensures all team members use consistent linting rules and formatting settings, preventing configuration drift and maintaining code quality standards across the project.
+If you're using Herb in a project with multiple developers, it's highly recommended to create a `.herb.yaml` configuration file and commit it to your repository. This ensures all team members use consistent linting rules and formatting settings, preventing configuration drift and maintaining code quality standards across the project.
 :::
 
 ### Creating a Configuration File
 
-To create a `.herb.yml` configuration file in your project, run either CLI tool with the `--init` flag:
+To create a `.herb.yaml` configuration file in your project, run either CLI tool with the `--init` flag:
 
 ```bash
 # Create config using the linter
@@ -59,13 +59,13 @@ This will generate a configuration file with sensible defaults:
 The CLIs support a `--force` flag to override project configuration:
 
 ```bash
-# Force linting even if disabled in .herb.yml
+# Force linting even if disabled in .herb.yaml
 herb-lint --force app/views/
 
 # Force linting on a file excluded by configuration
 herb-lint --force app/views/excluded-file.html.erb
 
-# Force formatting even if disabled in .herb.yml
+# Force formatting even if disabled in .herb.yaml
 herb-format --force --check app/views/
 ```
 
@@ -75,7 +75,7 @@ When using `--force` on an explicitly specified file that is excluded by configu
 
 Configure the linter behavior and rules:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 linter:
   enabled: true  # Enable/disable linter globally
 
@@ -182,7 +182,7 @@ linter:
 
 Example:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 linter:
   rules:
     # This rule only runs on component files, excluding legacy ones
@@ -206,7 +206,7 @@ linter:
 
 Configure the template engine behavior:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 engine:
   validators:
     security: true       # Enable/disable security validation (default: true)
@@ -226,7 +226,7 @@ When a validator is disabled (`false`), the engine skips it entirely during comp
 
 ### Validation Mode
 
-The `validation_mode` controls how the engine handles validation results. This is set programmatically when creating an `Herb::Engine` instance, not in `.herb.yml`:
+The `validation_mode` controls how the engine handles validation results. This is set programmatically when creating an `Herb::Engine` instance, not in `.herb.yaml`:
 
 - **`:raise`** (default): Raises an exception when validation errors are found
 - **`:overlay`**: Renders validation errors as an in-browser overlay (used by [ReActionView](https://github.com/marcoroth/reactionview) in development)
@@ -249,7 +249,7 @@ Herb::Engine.new(source, validation_mode: :none)
 
 ### Overriding Validators Programmatically
 
-Validator settings from `.herb.yml` can be overridden when creating an engine instance:
+Validator settings from `.herb.yaml` can be overridden when creating an engine instance:
 
 **Disable security validator for this template only**
 ```ruby
@@ -269,7 +269,7 @@ Herb::Engine.new(source, validators: {
 
 Configure the formatter behavior:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 formatter:
   enabled: false     # Disabled by default (experimental)
   indentWidth: 2     # Number of spaces for indentation
@@ -294,14 +294,14 @@ formatter:
 - **`exclude`**: Array of glob patterns - Additional patterns to exclude from formatting (additive to defaults)
 
 ::: warning Experimental Feature
-The formatter is currently experimental. Enable it in `.herb.yml` and test thoroughly before using in production.
+The formatter is currently experimental. Enable it in `.herb.yaml` and test thoroughly before using in production.
 :::
 
 ## Top-Level File Configuration
 
 Global file configuration that applies to both linter and formatter:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 files:
   # Additional glob patterns to include (additive to defaults, applies to all tools)
   include:
@@ -326,7 +326,7 @@ File patterns are merged in the following order:
 
 Example:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 files:
   include:
     - '**/*.xml.erb'    # Applies to all tools
@@ -379,7 +379,7 @@ bundle exec herb config ../other-project/
 Running `bundle exec herb config .` displays:
 
 - **Project root**: The detected project root directory
-- **Config file**: Path to the `.herb.yml` file (or "(using defaults)" if none)
+- **Config file**: Path to the `.herb.yaml` file (or "(using defaults)" if none)
 - **Include patterns**: All patterns used to find files
 - **Exclude patterns**: All patterns used to exclude files
 - **Files**: List of included and excluded files with their status
@@ -390,7 +390,7 @@ Example output:
 Herb Configuration
 
 Project root: /path/to/project
-Config file:  /path/to/project/.herb.yml
+Config file:  /path/to/project/.herb.yaml
 
 Include patterns:
   + **/*.herb
@@ -434,7 +434,7 @@ Example output:
 Herb Configuration for Linter
 
 Project root: /path/to/project
-Config file:  /path/to/project/.herb.yml
+Config file:  /path/to/project/.herb.yaml
 
 Include patterns (files + linter):
   + **/*.html.erb
@@ -456,7 +456,7 @@ Files for linter (40 included, 7 excluded):
 
 ::: tip Debugging Configuration
 The `bundle exec herb config` command is useful for:
-- Verifying your `.herb.yml` is being read correctly
+- Verifying your `.herb.yaml` is being read correctly
 - Understanding why certain files are included or excluded
 - Debugging tool-specific patterns
 - Confirming the project root detection

docs/docs/projects/dev-server.md

@@ -36,7 +36,7 @@ The dev server consists of two parts:
 
   Herb:      0.10.1
   Project:   /path/to/project
-  Config:    .herb.yml
+  Config:    .herb.yaml
   Files:     453 templates indexed
   WebSocket: ws://localhost:8592
 

docs/docs/projects/engine.md

@@ -50,7 +50,7 @@ In addition to Erubi options, `Herb::Engine` supports:
 
 ## Validators
 
-The engine runs validators on parsed templates to catch errors before compilation. Each validator can be enabled or disabled via [`.herb.yml` configuration](/configuration#engine-configuration) or per-instance overrides.
+The engine runs validators on parsed templates to catch errors before compilation. Each validator can be enabled or disabled via [`.herb.yaml` configuration](/configuration#engine-configuration) or per-instance overrides.
 
 | Validator | Description |
 |---|---|
@@ -63,7 +63,7 @@ Disable security validator for this template:
 Herb::Engine.new(source, validators: { security: false })
 ```
 
-See [Engine Configuration](/configuration#engine-configuration) for `.herb.yml` configuration.
+See [Engine Configuration](/configuration#engine-configuration) for `.herb.yaml` configuration.
 
 ## Validation Mode
 
@@ -77,4 +77,4 @@ Controls how the engine presents validation results:
 
 [ReActionView](https://github.com/marcoroth/reactionview) registers `Herb::Engine` as the template handler for `.html.erb` and `.html.herb` files in Rails. It uses `validation_mode: :overlay` so validation errors appear as in-browser overlays during development instead of raising exceptions.
 
-Validator settings from `.herb.yml` are respected automatically — no ReActionView-specific configuration needed.
+Validator settings from `.herb.yaml` are respected automatically — no ReActionView-specific configuration needed.

javascript/packages/config/README.md

@@ -28,11 +28,11 @@ bun add @herb-tools/config
 
 ## Usage
 
-### `.herb.yml`
+### `.herb.yaml`
 
-The configuration is stored in a `.herb.yml` file in the project root:
+The configuration is stored in a `.herb.yaml` file in the project root:
 
-```yaml [.herb.yml]
+```yaml [.herb.yaml]
 version: 0.10.1
 
 linter:
@@ -51,8 +51,8 @@ formatter:
 
 The Herb tools follow this configuration priority:
 
-1. **Project configuration** (`.herb.yml` file) - Highest priority
+1. **Project configuration** (`.herb.yaml` file) - Highest priority
 2. **Editor settings** (VS Code workspace/user settings)
 3. **Default settings** - Fallback when no other configuration exists
 
-This allows teams to share consistent settings via `.herb.yml` while still allowing individual developer preferences when no project configuration exists.
+This allows teams to share consistent settings via `.herb.yaml` while still allowing individual developer preferences when no project configuration exists.