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

misobox

v0.2.0

Published

ferment your errors like miso

Downloads

3

Readme

misobox

Ferment your errors like miso - aka a simple error collection/note taking tool made with TS and oclif

oclif Version Downloads/week

What is this?

misobox is a lightweight CLI tool that captures and preserves error messages (from stderr) from your projects for later review. You can also add manual notes to the log, to keep track of what you were doing at the time or to add an issue that isn't caught by the automated error collection (i.e memory leaks).

Features

  • Error Collection: Automatically captures stderr output from any command
  • Note Taking: Add manual notes alongside automated error collection
  • Compressed Storage: Stores error logs in a GZip compressed JSONL format
  • Universal Support: Works with any command-line tool or script

Usage

Using misobox is simple, just install it with you package manager of choice and run your commands with misobox run or add manual notes with misobox add.

# Install misobox
npm install -g misobox

# Run a command and log errors
misobox run -- gcc -o myprog myprog.c

# Add a note manually
misobox add "Need to fix memory leak in worker thread"

After running misobox run or misobox add, a file containing all the notes will be created in the current folder (.misobox).

You can use misobox to:

  • Log test failures for later investigation
    misobox run npm test
  • Track non fatal compilation errors
    misobox run -- gcc -o myprog myprog.c
  • Take notes about issues you encounter
    misobox add "Need to fix memory leak in worker thread"

Commands

misobox add [NOTE]

Adds a note to the misobox.

USAGE
  $ misobox add [NOTE...]

ARGUMENTS
  NOTE...  Text of the note to add

DESCRIPTION
  Adds a note to the misobox.

EXAMPLES
  $ misobox add

  $ misobox add foo bar

See code: src/commands/add.ts

misobox clear

Clears the misobox.

USAGE
  $ misobox clear

DESCRIPTION
  Clears the misobox.

EXAMPLES
  $ misobox clear

See code: src/commands/clear.ts

misobox help [COMMAND]

Display help for misobox.

USAGE
  $ misobox help [COMMAND...] [-n]

ARGUMENTS
  COMMAND...  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for misobox.

See code: @oclif/plugin-help

misobox recall

Displays a note from the misobox.

USAGE
  $ misobox recall

DESCRIPTION
  Displays a note from the misobox.

EXAMPLES
  $ misobox recall

See code: src/commands/recall.ts

misobox remove

Removes one or more notes from the misobox.

USAGE
  $ misobox remove

DESCRIPTION
  Removes one or more notes from the misobox.

EXAMPLES
  $ misobox remove

See code: src/commands/remove.ts

misobox run [COMMAND]

Run command and log errors into the misobox.

USAGE
  $ misobox run [COMMAND...] [-c <value>] [-v]

ARGUMENTS
  COMMAND...  Command to execute, add -- to pass flags to the command

FLAGS
  -c, --context=<value>  Grabs the last n lines of stdout and logs them when an error occurs
  -v, --verbose          Print more info while running

DESCRIPTION
  Run command and log errors into the misobox.

EXAMPLES
  $ misobox run echo hello

  $ misobox run -- ping -c 4 example.com

See code: src/commands/run.ts

Notes

  • When using misobox run, you can add "--" to prevent misobox from parsing them:

    # -c will be parsed by ping and misobox
    misobox run ping -c 4 example.com
    
    # -c will be parsed only by ping
    misobox run -- ping -c 4 example.com
  • misobox stores its data in a GZip compressed JSONL file. To make file operations faster, misobox only compresses a note when it's added, the file is never recompressed with normal use. To fix this, misobox remove will recompress the whole file after removing the selected notes (if no notes are selected it will just recompress the file).

  • Sometimes stdout and stderr are misalligned, this happens when a command is printing a lot of data quickly because of how node buffers stdout and stderr. Unfortunally, I haven't found a way to fix this yet, but I'm open to suggestions.

  • Some commands won't output color by default, for example ls (even if colored in your terminal), won't output color when run with misobox. In this case it's because ls is actually an alias for ls --color=auto, which misobox doesn't use. Other commands like gcc use their own method to detect if they're being run in a terminal and output color accordingly, which I still haven't figured out, so they won't output color either.