# nsx module search

Search the packaged or app-effective registry using module metadata and optional target-compatibility filters.

## Usage

```text
nsx module search [-h] [--app-dir APP_DIR] [--board BOARD] [--soc SOC]
                         [--toolchain TOOLCHAIN] [--include-incompatible]
                         [--json]
                         query
```

## Arguments

| Option | Value | Default | Description |
| --- | --- | --- | --- |
| query | value | required | Search query such as pmu, profiling, uart, or logging |

## Options

| Option | Value | Default | Description |
| --- | --- | --- | --- |
| --app-dir APP_DIR | value | optional | Optional app directory containing nsx.yml; when provided, use the app-effective registry and app target context |
| --board BOARD | value | optional | Optional board compatibility filter |
| --soc SOC | value | optional | Optional SoC compatibility filter |
| --toolchain TOOLCHAIN | value | optional | Optional toolchain compatibility filter |
| --include-incompatible | flag | optional | Include matches that fail the active compatibility filters |
| --json | flag | optional | Emit machine-readable JSON instead of human-readable text |

`-v/--verbose`, `-q/--quiet` are parsed by `nsx` itself, so they go before the command name, as `nsx -v module search`.