# workspace-eject

Make a managed Megamono workspace artifact repository-owned


## When to use it

Take over a file previously managed by Megamono so you can maintain it yourself. Review the path before applying; future synchronization will no longer manage that file for you.

## Usage

```sh
npm exec -- nx generate @megamono/plugin:workspace-eject --artifact="<artifact>" --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/plugin:workspace-eject`. 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 |
| --- | --- | --- | --- | --- |
| `artifact` | Yes | string | — | Which managed artifact should become repository-owned? |
| `dryRun` | No | boolean | false | Print the ejection plan without changing content or ownership state. |

## 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)