kubb list
Run kubb list to see the Kubb extensions installed in the current project, the version the Kubb registry pins for each, and whether an update exists. It takes no arguments or options.
Usage
kubb listID PACKAGE INSTALLED REGISTRY UPDATE
kubb-labs/plugin-ts @kubb/plugin-ts 5.4.2 5.4.4 yes
kubb-labs/plugin-zod @kubb/plugin-zod 5.4.4 5.4.4 no
- @acme/kubb-plugin-graphql 1.0.0 - noColumns
| Column | Description |
|---|---|
ID | The registry id, or - when the registry does not list the package. |
PACKAGE | The npm package name. |
INSTALLED | The version in node_modules, or - when the package is not installed. |
REGISTRY | The version the registry pins, or - when the registry does not list the package. |
UPDATE | yes when the installed version is older than the pinned one, or unknown. Run kubb update to install it. |
Which packages it lists
The CLI reads the dependencies and devDependencies in package.json of the current directory. It lists each package that ships a valid kubb-extension.json or has an entry in the registry index.
Extensions that ship inside kubb, such as @kubb/adapter-oas and @kubb/plugin-barrel, appear only when package.json lists them directly.
When the registry cannot be read, the CLI prints Showing installed extensions only: <reason> and lists the packages that ship a manifest. When it finds nothing, it prints No installed extensions found.
Environment variables
| Variable | Default | Description |
|---|---|---|
KUBB_REGISTRY | https://kubb.dev/registry | Base URL of the registry to read. See Host your own registry. |
Exit codes
kubb list exits with code 1 when KUBB_REGISTRY is not an http:// or https:// URL. A registry that cannot be reached does not fail the command.
See also
kubb add: install an extension from the registrykubb update: move installed extensions to the pinned version