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

@dolphindepot/bnr-cli

v0.1.0

Published

CLI tool to create and inspect Nintendo GameCube opening.bnr files

Downloads

137

Readme

@dolphindepot/bnr-cli

CLI tool to create and inspect Nintendo GameCube opening.bnr files.

Every GameCube disc contains an opening.bnr file with a 96x32 banner image and text metadata (game title, developer, description) shown by the system menu. Two formats exist:

  • BNR1 - US/JP region, single language
  • BNR2 - Europe (PAL), six languages (EN, DE, FR, ES, IT, NL)

Install

npm install -g @dolphindepot/bnr-cli

Or run without installing:

npx --yes @dolphindepot/bnr-cli <command>

Usage

Decode a .bnr file

Extract the banner image as PNG and text metadata as JSON:

bnr decode opening.bnr
# writes opening.png + opening.json

bnr decode opening.bnr -o output/
# writes output/opening.png + output/opening.json

Output JSON for BNR1:

{
    "type": "BNR1",
    "text": {
        "gameNameShort": "My Game",
        "developerNameShort": "Dev",
        "gameTitle": "My Game: Full Title",
        "developerName": "Developer Studio",
        "description": "A short game description."
    }
}

Output JSON for BNR2:

{
    "type": "BNR2",
    "texts": [
        { "gameTitle": "My Game", "description": "English description", "..." : "..." },
        { "gameTitle": "Mein Spiel", "description": "Deutsche Beschreibung", "...": "..." },
        "... (FR, ES, IT, NL)"
    ]
}

Encode a .bnr file

From CLI arguments

bnr encode \
  --image banner.png \
  --title "My Game" \
  --short-title "MyGame" \
  --developer "Dev Studio" \
  --short-developer "Dev" \
  --description "A cool homebrew game." \
  -o opening.bnr

From a JSON file

bnr encode --meta game.json -o opening.bnr

Where game.json looks like:

{
    "type": "BNR1",
    "image": "banner.png",
    "text": {
        "gameTitle": "My Game",
        "gameNameShort": "MyGame",
        "developerName": "Dev Studio",
        "developerNameShort": "Dev",
        "description": "A cool homebrew game."
    }
}

CLI arguments override JSON values:

bnr encode --meta game.json --title "New Title" -o opening.bnr

BNR2 with per-language text

Use language-suffixed flags (-en, -de, -fr, -es, -it, -nl) to set text per language. Unsuffixed flags set the base for all languages:

bnr encode --type BNR2 --image banner.png \
  --title "My Game" \
  --developer "Dev Studio" \
  --description "English description" \
  --description-de "Deutsche Beschreibung" \
  --description-fr "Description en francais" \
  -o opening.bnr

Or provide all translations in JSON:

{
    "type": "BNR2",
    "image": "banner.png",
    "texts": [
        { "gameTitle": "My Game", "description": "English", "...": "..." },
        { "gameTitle": "Mein Spiel", "description": "Deutsch", "...": "..." },
        { "gameTitle": "Mon Jeu", "description": "Francais", "...": "..." },
        { "gameTitle": "Mi Juego", "description": "Espanol", "...": "..." },
        { "gameTitle": "Il Mio Gioco", "description": "Italiano", "...": "..." },
        { "gameTitle": "Mijn Spel", "description": "Nederlands", "...": "..." }
    ]
}

Newlines

Use \n in CLI arguments for line breaks:

bnr encode --description "Line one\nLine two" --image banner.png -o opening.bnr

In JSON files, standard JSON escaping works as expected.

CI usage

Generate opening.bnr as part of your build pipeline:

- run: npx --yes @dolphindepot/bnr-cli encode --meta game.json -o opening.bnr