Commands
The tapid CLI, organised by command and implementation status.
tapid's CLI is intentionally explicit. Each command has a narrow responsibility, documented inputs, and a clear boundary when the current client cannot complete an operation.
Command reference
tapid initcreates a privatepackage.jsonwithout overwriting an existing file.tapid manifest validatevalidates a selected manifest before project work.tapid lock verifyvalidates the lockfile in the current project.tapid installreplays or installs project dependencies through the currently supported paths.tapid runruns an explicit rootpackage.jsonscript and forwards arguments.tapid upgradeis documented as a not-currently-supported self-update path.
Status language
Each page labels behavior as implemented, constrained, or not currently supported. A command can be implemented while still having important limits. Examples stay within behavior verified for the current development target.
How the commands fit together
Use init when a directory needs its first private package.json. Use manifest validate when you want to check that file without changing it. Use install to resolve packages, write tapid.lock, and materialize managed node_modules. Use lock verify for a structural lockfile check, then use offline or frozen install when you need to replay the verified project inputs. Use run only for scripts explicitly declared in the root manifest.
The current CLI does not expose a self-update command. To upgrade Tapid, rerun the public installer described in Getting started.
Typical installation path
Install the latest published release, create a project, and install one supported package:
Install Tapid 0.0.9
Download the installer from the version tag, inspect it, and run it with the same explicit version.
macOS and Linux
Windows PowerShell
The public installer selects a stable GitHub release and verifies its archive checksum before replacing the installed binary. The latest release page lists every native archive, SHA256SUMS, and the release notes fetched from GitHub during the website build. Tapid supports a bounded npm-compatible subset. Read the install command page before evaluating a project that depends on tags, aliases, peers, workspaces, private registries, lifecycle scripts, or other npm-specific behavior. For source builds and repository checks, read Contributor.