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

@enke.dev/logbox

v0.0.7

Published

Wraps a long-running command and pins a configurable info box to the bottom of the terminal.

Readme

logbox

Wraps a long-running command and pins a configurable info box to the bottom of the terminal. The wrapped command's output scrolls above it, unaltered — colors, spinners and all.

[dev:docs] vite v7.1.0 ready in 431 ms
[dev:components] build started…
╭─ dev servers ──────────────────────────────────────────────────────╮
│ docs........................................https://localhost:5173 │
│ components (web)............................https://localhost:5174 │
│ components (react)..........................https://localhost:5175 │
╰────────────────────────────────────────────────────────────────────╯

tl;dr

# invoke directly
npx @enke.dev/logbox pnpm -r --parallel --stream dev
pnpm dlx @enke.dev/logbox pnpm -r --parallel --stream dev
bunx --bun @enke.dev/logbox pnpm -r --parallel --stream dev

# or install and run globally
npm i -g @enke.dev/logbox
logbox pnpm -r --parallel --stream dev

Typical use is a package.json script:

{
  "scripts": {
    "dev": "logbox pnpm -r --parallel --stream dev:*"
  }
}

How it works

The box lives in terminal lines that are reserved by shrinking the scroll region, so it is not part of the output stream: nothing scrolls it away, and nothing is rewritten or filtered on the way through. Redraws are coalesced, so a burst of output costs one render.

Without a TTY (pipes, CI logs) there is nothing to pin the box to, so the content is printed once up front as a flat list and the child inherits stdio directly.

Signals (SIGINT, SIGTERM, SIGHUP) are handed down to the child, which decides when to go away. logbox exits with the child's exit code, so it stays transparent in scripts.

Configuration

Content is an array of rows; each row is an array of strings:

  • the first cell is left aligned,
  • the last cell is right aligned,
  • a dot leader connects them,
  • middle cells (3+ per row) get their own aligned column,
  • a row with a single cell renders as a plain label.

.logbox.json

Looked up in the current directory, then every parent up to the filesystem root — so a file in the repo root is found from any nested cwd — and finally in the user home directory (~/.logbox.json) as a global fallback.
The nearest file wins.

Bare rows:

[
  ["docs", "https://localhost:5173"],
  ["components", "https://localhost:5174"]
]

Or the object form, which adds a title:

{
  "$schema": "https://enke-dev.github.io/logbox/logbox.schema.json",
  "title": "dev servers",
  "content": [
    ["docs", "https://localhost:5173"],
    ["components", "https://localhost:5174"]
  ]
}

The JSON schema is published at https://enke-dev.github.io/logbox/logbox.schema.json — reference it via $schema for editor completion and validation.

Inline

--content takes the same JSON and skips the file lookup entirely:

logbox -c '[["docs","https://localhost:5173"]]' -t 'dev servers' npm run dev

Options

Only the options ahead of the wrapped command belong to logbox — everything from the first non-flag token on is passed through verbatim, so the wrapped command keeps its own flags (logbox pnpm -r --parallel dev). Use -- if the command itself starts with a dash.

| Option | Description | | ---------------------- | --------------------------------------------------------- | | -c, --content <json> | Box content as inline JSON; overrides any config file | | -t, --title <text> | Title rendered into the top border (default: logbox) | | --config <path> | Read the content from this file instead of looking one up | | -h, --help | Show help | | -v, --version | Print the version |

With no content configured anywhere, logbox draws no box and simply runs the command.

Development

bun install
bun run dev -c '[["a","b"]]' -- sleep 5   # run from source
bun run check                             # types
bun run lint                              # eslint + prettier
bun run test                              # specs under bun and node
bun run build                             # dist/cli.mjs

Releases are trunk based: pushing to main cuts the semver release from the conventional commits since the last tag and republishes the schema to GitHub Pages.

License

MIT