npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@usedoku/cli

v0.0.3

Published

The Doku command-line interface.

Downloads

446

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

batuhndevbatuhndev

Keywords

Readme

@usedoku/cli

The Doku command-line interface.

Use this package for local Doku login, development sync, Git helper setup, repo status, MCP connection flows, and narrow sandbox fixture operations.

npm install -g @usedoku/cli
doku auth status

The published doku executable runs with Bun. Install Bun 1.3 or newer and keep bun on PATH before running the global binary.

Command Discovery

The CLI uses Clipanion for typed command routing and command-specific help. Agents should discover commands through the CLI itself:

doku help
doku help --json
doku collections copy --help

doku help --json is the stable agent-readable command catalog. It includes paths, summaries, options, environment fallbacks, examples, and JSON support. Keep command metadata in src/cli/command-catalog.ts when adding or changing a command so human help, agent discovery, and docs do not drift.

Runtime Boundary

The CLI is an Effect-powered command runtime. Clipanion command classes are thin syntax adapters; command behavior should live behind Effect-backed handlers, services, and plain Promise-returning package boundaries. Project-facing authoring APIs live in @usedoku/sdk and runtime site helpers live in @usedoku/site.

The hosted MCP surface is for Project-scoped CodeMode runtime work, especially brokered Integrations. It does not mirror the CLI command catalog. Local project operations such as doku dev, doku init, repo status/actions, MCP config installation, and sandbox fixture commands remain CLI-owned.

Collections Fixtures

Content Collections fixture commands are development and preview helpers, not general Content Item authoring commands.

  • doku collections seed reads doku.seed.json by default, preflights dev fixtures against locally compiled collection schemas, and writes explicit items to the target sandbox. Use --target preview with --sandbox or --preview-key to seed preview data with remote sandbox validation.
  • doku collections reset --yes deletes Content Collections data only. It does not reset Forms, Workflows, Analytics, secrets, manifests, or whole sandbox state. Use --target preview with --sandbox or --preview-key for preview reset.
  • doku collections copy supports production-to-dev, production-to-preview, and dev-to-preview fixture paths. Use --collection --limit for bounded samples or --items for explicit Content Item IDs.

Dev targets default to .doku/dev.env; --sandbox overrides the target sandbox. Preview targets must be explicit through --sandbox or --preview-key. --ensure-preview is the only path that creates preview fixture state.

Copy is bounded, idempotent by source Content Item identity, non-recursive for references in v1, and partial-success by default. Fixture copy authorization uses operator permissions on the source and target sandboxes; Content Collection public/private site-runtime visibility is not the authority model.

Preview deployments do not implicitly copy dev sandbox data. Production seed and production reset are out of scope; production content changes use normal authorized Production Content Operations.