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

@lunibee/cli

v0.4.0

Published

Lunibee workspace and developer CLI.

Readme

@lunibee/cli

The lunibee command: create a bot project, scaffold components, migrate code to 0.4.0, and check a project.

bun add -d @lunibee/cli
bunx lunibee help
bunx @lunibee/cli init my-bot   # a new project

Commands

| Command | What it does | |---|---| | lunibee init [directory] | Create a new bot project: src/index.ts (startup), config.ts (validated .env), commands and events found recursively at runtime under src/commands and src/events, services/register.ts (registers the commands with Discord on every start: in GUILD_ID's server, or globally), /ping, logger, README, .env.example, tsconfig.json. The folder name is the package name. Existing files are never overwritten without --force, which asks first (--yes confirms without a prompt). --install runs bun install (the CLI and the project need Bun 1.4+); --dry-run. Files are staged first, so a failed write leaves nothing half-created. | | lunibee create component [button\|select\|modal] [name] | Create src/components/<name>.ts with the builder (row() or modal()), its customId and a handle(client, interaction) stub. The name is the custom ID (1-100 of a-z A-Z 0-9 _ - : .). Options: --force, --dry-run. | | lunibee migrate [--fix] | Find APIs removed in 0.4.0 in the TypeScript and JavaScript files under src/. --fix renames the removed names (Events → ClientEvent, CreateStringSelectMenu → CreateStringSelect, Status → GatewayState…) only in files that import them from lunibee or @lunibee/*, so names imported from other packages are never touched; import { X as Y } keeps Y. Code it cannot rewrite is listed with file:line and its replacement. Exit 1 while anything is left. --dry-run, --json. | | lunibee list <handlers\|commands\|components\|events> | List the modules under src/events, src/commands or src/components (recursive, the files an init project loads: no .d.ts, tests, or names starting with _), or every client event. --json. | | lunibee check | Project layout; loads the commands and events through the project's src/handlers/commands.ts and src/handlers/events.ts (invalid modules, duplicate names); .env present with a token key, ignored by git, and with every key of .env.example. Exit code 1 on errors. --json. | | lunibee doctor | Everything check does, plus the Bun version, installed Lunibee packages (missing or mixed versions) and tsconfig.json strictness. --json. | | lunibee info | Project, declared and installed Lunibee versions, event/command/component file counts, runtime and CLI version. --json. | | lunibee status | Lunibee maintainers: every package in the monorepo the CLI runs from, flagging mixed versions. --json. | | lunibee publish | Lunibee maintainers: bun publish every non-private package, dependencies first. Refuses mixed versions; asks for confirmation unless --yes. Options: --dry-run, --tag, --otp. |

Global options: --cwd <dir> runs in another project (the project root is the nearest folder with a package.json, so any subfolder works), --no-color (or NO_COLOR), -h/--help on any command, -v/--version. Unknown commands, options and list kinds get a "did you mean" suggestion. Secrets are never printed: check only looks for the token key in .env, not its value, and loads the project's modules without the environment.

lunibee migrate lists every rename and hand change; see the CLI page for the full list. 0.4.0 removed the binder-layout commands (create handler, create command, sync handlers, sync commands, handler --fix) and the @lunibee/create package: use lunibee init.