skmtc remove

remove is the dual of install/clone/create. It strips the generator's entry from deno.json#imports and, when the entry pointed at a local path (a clone or a local-create), deletes the source directory under .skmtc/<project>/<generator>/. remove does not rebundle and does not update the Deno lockfile — the next bundle or generate invocation is responsible for those.

Synopsis

skmtc remove [project] [generator] [--json] [--no-input]

Arguments

[project]

The target project name. Required in strict mode.

[generator]

The generator name to remove (the import key in deno.json#imports). Required in strict mode.

When unset (and not in strict mode), the CLI prompts with the project's installed generators.

Options

--no-input

Disable interactive prompts.

--json

Write JSON output to stdout. Implies --no-input.

Behavior

deno.json imports updated

The CLI removes the matching entry from .skmtc/<project>/deno.json#imports:

// Before:
{
  "imports": {
    "@skmtc/gen-zod": "jsr:@skmtc/gen-zod@^0.0.55",
    "@skmtc/gen-msw": "jsr:@skmtc/gen-msw@^0.0.30"
  }
}

// After (removing @skmtc/gen-zod):
{
  "imports": {
    "@skmtc/gen-msw": "jsr:@skmtc/gen-msw@^0.0.30"
  }
}

The Deno lockfile is not touched by remove. Stale entries are pruned the next time Deno re-resolves imports (e.g., on the next bundle or generate).

Cloned-source directory handling

When the removed generator's import points at a local path (clone or create source), the CLI also deletes the source directory:

.skmtc/<project>/<generator>/   ← deleted

This is irreversible. If you have uncommitted changes in the generator's source, commit them (or move them) before running remove. The CLI does not check for git-dirty state.

For JSR (jsr: specifier) sources, no source directory exists to delete — only the import entry is removed.

remove does not rebundle

remove does not invoke bundle. If you removed a local generator and the project still has other locals, the existing bundle.js becomes stale — run skmtc bundle <project> (or rely on the next generate's freshness check) to rebuild.

Cascading dependencies

If other generators in the project import the removed one (a rare but possible case), the next bundle will fail. The fix is to either restore the generator (re-install) or update the dependent generator's source to drop the import.

JSON output

{
  "projectName": "my-api",
  "removed": "@skmtc/gen-zod"
}

The shape matches RemoveHeadlessResult in cli/lib/remove-headless.ts:15-18:

export type RemoveHeadlessResult = {
  projectName: string
  removed: string
}

That's the entire payload. There is no command envelope, no source classification, no directoryDeleted field, no bundle field, no verifyWith hint. The output reports only which generator was removed from which project. Side effects (deno.json mutation, local source directory delete) are silent — verify them yourself via skmtc list <project> --json and a filesystem check on .skmtc/<project>/<generator>/.

Examples

Remove a JSR generator

skmtc remove my-api @skmtc/gen-zod

Removes the import entry. Rebuild the bundle (skmtc bundle my-api) before the next generate so the removed generator drops out of bundle.js — strict-mode generate refuses on the drift otherwise.

Remove a local generator (with source deletion)

skmtc remove my-api @dgrabov/my-form --json

Strict mode. Removes the import entry from deno.json#imports and deletes .skmtc/my-api/my-form/. No rebundle is performed — run skmtc bundle my-api afterwards if you want the existing bundle.js refreshed.

Scripted batch removal

for gen in @skmtc/gen-msw @skmtc/gen-zod; do
  skmtc remove my-api "$gen" --json
done

Or use skmtc list --json to discover what's installed first.

Exit codes

Common failure modes

Generator not found

Error: generator '@skmtc/gen-foo' not in project 'my-api'

The import key doesn't match anything in deno.json#imports. Run skmtc list my-api to see what's actually installed.

Stale bundle after removal

remove itself does not rebundle. If you removed a local generator, the project's bundle.js no longer reflects the source tree. The next bundle or generate will pick up the change; until then, a direct generate run uses the stale bundle and may still produce artifacts from the removed generator.

Source-directory delete failure

Error: failed to delete .skmtc/my-api/my-form: permission denied

The deno.json#imports removal succeeded but the directory delete didn't. The generator is "removed" from the project's logical state but the source files remain. Inspect the directory manually.

What remove does not do

• Does not remove entries from client.json (enrichments, paths). Those may now point at a generator that no longer exists, which is harmless but cluttered. Manual cleanup if needed.
• Does not verify git state — uncommitted changes in a clone/local generator's source are deleted with the directory.
• Does not undo edits the removed generator made to your generated artifacts on previous runs. Those artifacts remain on disk; next generate may stop producing them, and your tracked files will have an unmaintained generator's output until you clean it up.

See also

• skmtc install — the inverse for JSR generators
• skmtc clone — the inverse for cloned generators
• skmtc create — the inverse for local-created generators
• skmtc list — verify what's installed before/after
• skmtc bundle — rebuild bundle.js after removing a local generator
• Clone vs install concept — context for the three source kinds