@emdash-cms/registry-cli

CLI for the experimental EmDash plugin registry.

EXPERIMENTAL: bundle, login, whoami, switch, and publish all work today against any atproto PDS — publish writes profile + release records to the publisher's own repo. The discovery commands (search, info) need an aggregator; none is deployed yet, so those won't return useful results until one is. NSIDs and shapes will change while RFC 0001 is in flight; pin to an exact version.

Installation

npx @emdash-cms/registry-cli bundle

Or install globally:

npm install -g @emdash-cms/registry-cli
emdash-registry bundle

Commands

emdash-registry login <handle-or-did>          Interactive atproto OAuth login
emdash-registry logout [--did <did>]           Revoke the active session
emdash-registry whoami                         Show stored sessions
emdash-registry switch <did>                   Switch the active publisher session
emdash-registry search <query>                 Free-text search
emdash-registry info <handle-or-did> <slug>    Show package details
emdash-registry bundle                         Bundle a plugin source dir into a tarball
emdash-registry publish --url <url>            Publish a release that points at a hosted tarball

All commands accept --json. Discovery commands accept --aggregator <url> (or EMDASH_REGISTRY_URL).

Publishing

Three steps. The CLI does not host artifacts — you do, anywhere public.

emdash-registry bundle
# upload dist/<id>-<version>.tar.gz somewhere public
emdash-registry publish --url https://example.com/foo-1.0.0.tar.gz

On first publish, pass --license and --security-email (or --security-url) to bootstrap the package profile.

Programmatic API

import { bundlePlugin } from "@emdash-cms/registry-cli";

const result = await bundlePlugin({ dir: "./my-plugin" });

For discovery and credentials, import from @emdash-cms/registry-client.