# Extension application

Create a WXT browser extension application


## When to use it

Create a WXT browser extension application. Use this when you want to add the corresponding files or task to your workspace.

## Usage

```sh
npm exec -- nx generate @megamono/nx-extension:application --name="<name>" --dry-run
```

Replace angle-bracket placeholders with reviewed values. Nx's `--dry-run` previews generator writes; remove it only after reviewing the plan. Examples use npm; use your workspace's package manager if it differs.

## Options

Use these options with `@megamono/nx-extension:application`. Nx uses the camelCase names shown here; the [CLI reference](/docs/cli) describes command-line aliases. Some options are required only for particular choices.

| Option | Required | Type | Default | Description |
| --- | --- | --- | --- | --- |
| `name` | Yes | string | — | — |
| `projectName` | No | string | — | — |
| `directory` | No | string | — | — |
| `scope` | No | string | — | — |
| `tags` | No | string | — | — |
| `displayName` | No | string | — | — |
| `contentScriptMatches` | No | array | — | Opt in to a content script with explicit browser match patterns. Omit for a background-only extension with no page access. |
| `manifestVersion` | No | number | — | Explicit manifest version for Chrome and Firefox. Omit to retain WXT configuration/defaults. Allowed: 2, 3. |
| `skipFormat` | No | boolean | false | — |
| `skipInstall` | No | boolean | false | Defer installation and peer verification to the caller; preserve their package-manager/store policy. |

## Next steps

Review changed files and run the affected project's checks. For options that accept structured values, run the generator's `--help` or consult the schema in the installed package.

- [All generators](/docs/generators)
- [CLI overview](/docs/cli)
- [Adopt an existing workspace](/docs/workflows/adoption)