# tapid prune

Source: https://tapid.dev/docs/commands/prune

Rebuild managed node_modules from a verified lockfile without network access.

## Status

Available starting with published v0.0.11. This page targets v0.0.13. Read [Compatibility](https://tapid.dev/docs-markdown/compatibility/content.md) for the supported subset and [Release changes](https://tapid.dev/docs-markdown/development/content.md) for the reviewed release changes.

## Syntax

```text
tapid prune [OPTIONS]
```

```bash
$ tapid prune
$ tapid prune --store-dir ./verified-store
```

Requires a matching `package.json`, a valid `tapid.lock`, and every referenced verified package tree. It uses frozen replay to atomically replace managed `node_modules` and remove stale materialized packages.

It does not resolve new versions, access the network, or delete cached store trees. It is not store garbage collection. Missing or mismatched replay inputs fail instead of triggering an online install. `--registry-fixture` and `--allow-unverified-registry-artifacts` have no effect on this command.

## Shared options

* `--project-dir PATH` selects the project, defaulting to the current directory.
* `--workspace NAME` selects a workspace member by name. The root owns the lockfile and managed activation. See [Workspaces](https://tapid.dev/docs-markdown/workspaces/content.md) for member selection and local-link limits.
* `--store-dir PATH` selects the verified store where applicable.
* `--registry-fixture PATH` supplies local metadata for tests where applicable.
* `--allow-unverified-registry-artifacts` permits the explicit online integrity exception where applicable. Resulting installs cannot use offline/frozen replay.

This command does not execute dependency lifecycle scripts. Check `tapid prune --help` on your installed binary before execution. The command does not provide a package safety verdict.