# Component Schema

Component configuration defines buildable and deployable units stored in `components/<id>.json`.

## Schema

```json
{
  "id": "string",
  "name": "string",
  "local_path": "string",
  "remote_path": "string",
  "build_artifact": "string",
  "extract_command": "string",
  "version_targets": [
    {
      "file": "string",
      "pattern": "string"
    }
  ],
  "changelog_target": "string",
  "scripts": {
    "lint": ["shell command"],
    "test": ["shell command"],
    "build": ["shell command"],
    "bench": ["shell command"],
    "trace": ["shell command"]
  },
  "extensions": {},
  "release": {}
}
```

## Fields

### Required Fields

- **`id`** (string): Unique component identifier, derived from `local_path` directory name (lowercased)
- **`local_path`** (string): Absolute path to local **source / git checkout** directory, `~` is expanded
- **`remote_path`** (string): Remote path relative to project `base_path` (the **deploy target**)
- **`build_artifact`** (string): Build artifact path relative to `local_path`, must include filename

> **Important:** `local_path` must point to a **git repository / source checkout**, not the production deploy target. The deploy target is derived from `project.base_path + component.remote_path`. If `local_path` points to the deployed directory, builds will run inside production and uncommitted-changes checks will fail (the directory isn't a git repo). This is a common misconfiguration after server migrations.

### Optional Fields

- **`name`** (string): Human-readable component name, defaults to `id`
- **`extract_command`** (string): Command to execute after artifact upload, runs inside target directory
  - Supports template variables: `{artifact}`, `{targetDir}`
- **`version_targets`** (array): List of version detection patterns
  - **`file`** (string): Path to file containing version (relative to `local_path`)
  - **`pattern`** (string): Regex pattern to extract version (first capture group)
- **`changelog_target`** (string): Path to changelog file (relative to `local_path`)
- **`extensions`** (object): Extension-specific settings
  - Keys are extension IDs (e.g., `"wordpress"`, `"rust"`)
  - Values are extension setting objects
- **`scripts`** (object): Component-owned shell commands for extension-shaped capabilities
  - Supported keys: `lint`, `test`, `build`, `bench`, `trace`
  - Each value is an array of shell commands run sequentially in `local_path`
  - Resolution order is `scripts.<capability>` first, then linked extension support, then not-applicable
  - Scripts receive the same runner env paths (`HOMEBOY_COMPONENT_ID`, `HOMEBOY_COMPONENT_PATH`, `HOMEBOY_RUN_DIR` and sidecar file vars when relevant) as extension runners, with `HOMEBOY_EXTENSION_ID=component-script`
  - Use `scripts.build`, not `build_command`; `build_command` is still only a diagnostic output field.
- **`release`** (object): Component-scoped release configuration
  - **`enabled`** (boolean): Whether release pipeline is enabled
  - **`steps`** (array): Release step definitions
  - **`settings`** (object): Release pipeline settings

### Runtime Requirements

`homeboy component env` reports runtime requirements in a generic `runtimes` map:

```json
{
  "command": "component.env",
  "id": "example",
  "extension": "example-extension",
  "runtimes": {
    "php": { "version": "8.2", "source": "component" },
    "node": { "version": "22", "source": "extension:example-extension" }
  }
}
```

Runtime IDs are extension-owned strings. `source` is `component` for component config or detector output and `extension:<id>` for extension-provided defaults. Legacy component extension settings such as `{ "php": "8.2", "node": "22" }` are still parsed for compatibility; new config should use `runtimes`.

### Hook Fields

- **`pre_version_bump_commands`** (array of strings): Commands to run BEFORE version targets are updated
  - Execution: Sequential, runs in `local_path` directory
  - Failure behavior: **Fatal** - stops version bump on non-zero exit code
  - Use case: Validate generated sources before changing version files

- **`post_version_bump_commands`** (array of strings): Commands to run AFTER version files are updated
  - Execution: Sequential, runs in `local_path` directory
  - Failure behavior: **Fatal** - stops version bump on non-zero exit code
  - Use case: Regenerate files that depend on version, run linters, stage additional files

- **`post_release_commands`** (array of strings): Commands to run after the release pipeline completes
  - Execution: Sequential, runs in `local_path` directory
  - Failure behavior: **Non-fatal** - logs warnings but doesn't fail the release
  - Use case: Cleanup tasks, notifications, non-critical post-release actions

## local_path vs remote_path

```
local_path (source)                          remote_path (deploy target)
┌──────────────────────────┐                ┌──────────────────────────────────────────┐
│ ~/repos/extrachill-api/  │  ── build ──▶  │ /var/www/site/wp-content/plugins/        │
│ (git checkout, builds    │    deploy      │ extrachill-api/                          │
│  run here)               │                │ (project.base_path + remote_path)        │
└──────────────────────────┘                └──────────────────────────────────────────┘
```

- **`local_path`** — where the code lives on your dev machine (a git repo)
- **`remote_path`** — where it gets deployed on the server (relative to the project's `base_path`)

Setting `local_path` to the same directory as the deploy target is a misconfiguration — builds would run in production and `homeboy deploy` would fail uncommitted-changes checks.

## Example

```json
{
  "id": "extrachill-api",
  "name": "Extra Chill API",
  "local_path": "/Users/dev/extrachill-api",
  "remote_path": "wp-content/plugins/extrachill-api",
  "build_artifact": "build/extrachill-api.zip",
  "extract_command": "unzip -o {{artifact}} && rm {{artifact}}",
  "version_targets": [
    {
      "file": "composer.json",
      "pattern": "\"version\":\\s*\"([^\"]+)\""
    }
  ],
  "changelog_target": "CHANGELOG.md",
  "pre_version_bump_commands": [
    "./scripts/verify-generated-sources"
  ],
  "post_version_bump_commands": [
    "./scripts/refresh-versioned-artifacts"
  ],
  "post_release_commands": [
    "echo 'Release complete!'"
  ],
  "extensions": {
    "wordpress": {
      "settings": {
        "php_version": "8.1"
      }
    }
  },
  "release": {
    "enabled": true,
    "steps": [
      {
        "id": "test",
        "type": "extension.run",
        "label": "Run Tests",
        "config": {
          "extension": "rust"
        }
      }
    ]
  }
}
```

## Version Target Format

Version targets use regex to extract semantic versions from files. The pattern must include a capture group for the version string.

Common patterns:
- Composer: `\"version\":\\s*\"([^\"]+)\"`
- Cargo: `^version\\s*=\\s*\"([^\"]+)\"`
- Package.json: `\"version\":\\s*\"([^\"]+)\"`
- WordPress plugin header: `Version:\\s*([\\d.]+)`

## Extract Command Context

The `extract_command` runs inside the target directory after artifact upload. The working directory is:
- `project.base_path + component.remote_path`

Available template variables:
- **`{artifact}`** - The uploaded artifact filename only
- **`{targetDir}`** - Full target directory path

## Storage Location

Components are stored as individual JSON files under the OS config directory:
- **macOS/Linux**: `~/.config/homeboy/components/<id>.json`
- **Windows**: `%APPDATA%\homeboy\components\<id>.json`

## Related

- [Component command](../commands/component.md) - Manage component configuration
- [Hooks system](../architecture/hooks.md) - Lifecycle hooks for version and release operations
- [Project schema](project-schema.md) - How components link to projects
- [Extension manifest schema](extension-manifest-schema.md) - Extension configuration structure
