# verify-runtime

Verify production dependencies used by built JavaScript output


## When to use it

Check a built application for dependencies that may be missing when it runs outside your checkout. Build the application first. If its bundler loads modules dynamically, supply the corresponding build evidence and also test the deployed runtime.

## Usage

Configure an Nx target on the owning project, then invoke it with `npm exec -- nx run <project>:<target>`. The executor identifier is not a standalone CLI command.

```json
{
  "targets": {
    "reviewed-action": {
      "executor": "@megamono/plugin:verify-runtime",
      "options": {}
    }
  }
}
```

This target is a configuration example. Supply required values and review side effects before invoking it.

## Options

Use these options with `@megamono/plugin:verify-runtime`. 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 |
| --- | --- | --- | --- | --- |
| `project` | No | string | — | Nx project to verify; defaults to the target project. |
| `outputPath` | No | string | — | Workspace-relative built output path; otherwise inferred from the build target. |
| `buildTarget` | No | string | "build" | Project target used to infer the built output path. |
| `report` | No | string | — | Optional workspace-relative JSON report path. |
| `webpackEvidence` | No | string | — | Workspace-relative build-generated Webpack Node chunk evidence. Unknown loads still fail closed. |

## 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 actions](/docs/actions)
- [CLI overview](/docs/cli)
- [Adopt an existing workspace](/docs/workflows/adoption)