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

@nvwa-os/cli

v0.2.0

Published

Nvwa developer CLI (nvwa-os): login, integration-docs, ops, Agent run

Readme

@nvwa-os/cli

Unified Nvwa developer CLI. Terminal command: nvwa-os (npm package @nvwa-os/cli).

npm status

Not published to npm yet. npm install -g @nvwa-os/cli will fail until you publish from this monorepo.

Why local npm install -g fails today:

  • "private": true blocks accidental publish
  • @nvwa-os/common is a devDependency with workspace:* (monorepo only; runtime code is bundled into dist/cli.js)
  • @nvwa-os/common itself is not on npm

Use in monorepo (now)

bun run build:cli
packages/cli/bin/nvwa-os whoami
packages/cli/bin/nvwa-os login --project <code> --studio <url>

Requires Bun ≥ 1.1 (shebang in bin/nvwa-os).

After npm publish (future)

npx @nvwa-os/cli login --project <code> --studio https://studio.example.com
# or
npm install -g @nvwa-os/cli
nvwa-os whoami

Publish checklist (maintainer)

  1. bun run verify:pack (or repo root bun run verify:cli-pack) — must pass
  2. Remove "private": true from package.json (or publish from a release branch without it)
  3. Ensure packed dependencies has no workspace:* (verify script checks this)
  4. npm publish --access public from packages/cli
  5. Smoke: npx @nvwa-os/cli@latest whoami

Configure

Recommended: device login writes .nvwa/config.json (see Studio Agent 接入).

Config resolution priority (bundled from @nvwa-os/common):

  1. NVWA_INTEGRATION_DOCS_TOKEN + API base env
  2. env token + job.json integrationDocsHints (Agent Pod)
  3. ~/.nvwa/config.json + repo .nvwa/config.json

Commands

| Group | Command | Audience | |-------|---------|----------| | Auth | login logout whoami config path | External developers | | Integration docs | integration-docs contracts\|documents\|guides\|guide\|apis\|api | External + Agent Pod | | Deploy ops | ops deploy-status\|deploy-tree\|deploy-logs\|release-build-log | Agent Pod (Phase 3: external dev key) | | Agent run | run --mode cursor\|claude\|opencode | Agent Pod only |

Examples

nvwa-os login --project demo --studio https://studio.example.com
nvwa-os integration-docs apis --contract my-vendor --json
nvwa-os ops deploy-status

run is injected in K8s Agent Jobs; external users normally do not need it.

Optional MCP

@nvwa-os/integration-docs-mcp is a separate package for Cursor MCP. It reads the same config file or env when started from your business repo.

Build

bun run build   # → dist/cli.js (bundled for npm / local bin)

Verify publish artifact (build → npm pack → temp install → nvwa-os whoami):

bun run verify:pack
# or from repo root:
bun run verify:cli-pack

Agent image also bundles this entry via packages/agent/scripts/build-runtime.ts.