tapid add

Status

Available starting with published v0.0.11. This page targets v0.0.13. Read Compatibility for the supported subset and Release changes for the reviewed release changes.

Syntax

tapid add <PACKAGE>... [OPTIONS]

$ tapid add 'react@^19.0.0'
$ tapid add --dev 'typescript@^5.0.0'
$ tapid add --peer 'react@^19.0.0'

Use --dev, --optional, or --peer to select devDependencies, optionalDependencies, or peerDependencies. These flags are mutually exclusive. The default section is dependencies. A package without a requirement uses *. --peer records a peer declaration without installing it as an ordinary dependency.

The command retains compatible locked selections while resolving necessary changes to the resulting graph, verifies artifacts, and updates package.json, tapid.lock, and managed node_modules through the lifecycle transaction. Pre-commit failures restore prior state when rollback succeeds. Read Troubleshooting if cleanup or recovery fails.

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 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.

Dependency lifecycle scripts are denied by default. Exact checked-in approvals can execute supported hooks on Linux ManagedTree. Read Dependency scripts before approving execution. Check tapid add --help on your installed binary before execution. The command does not provide a package safety verdict.