tapid update

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 update [PACKAGE]... [OPTIONS]

$ tapid update
$ tapid update react
$ tapid update --latest react

Without package names, all direct dependencies are selected. By default, declared ranges stay unchanged. With --latest, selected requirements become * in package.json; aliases keep their target identity and change the target range. A name declared in several dependency sections is updated in each section.

Every update resolves the entire graph again. Selecting one package controls which declarations change, not which other locked packages can change during resolution. Review the resulting manifest and lockfile diff. The command performs an online lifecycle transaction and updates managed node_modules.

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 update --help on your installed binary before execution. The command does not provide a package safety verdict.