Megamono

DOCUMENTATION

On this page
  1. When to use it
  2. Usage
  3. Options
  4. Next steps

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

bash
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 describes command-line aliases. Some options are required only for particular choices.

OptionRequiredTypeDefaultDescription
artifactYesstring—Which managed artifact should become repository-owned?
dryRunNobooleanfalsePrint 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.

Megamono

One repository system for the applications, tools, and people building together inside it.

BUILD

Get startedGuidesDocumentationCLI referenceCapabilitiesInference

SOURCE

GitHub ↗

MIT licensed

© 2026 Megamono

By

Commune Software