bro-say

Build Buddy: useful summaries for real scripts (1.0.0)

Feed measured facts to summarizeBuild(input), or renderBuildSummary(input, options). A nonzero build exit, failed tests or explicit failure messages produces failed; exitCode: 0 produces passed; an absent/null exit code remains unknown. Passing test counts alone never invent a successful build. Missing measurements stay visible.

import { renderBuildSummary } from "@deployanyway/bro-say";
const result = renderBuildSummary({
  label: "Release build",
  exitCode: 1,
  durationMs: 1520,
  tests: { passed: 42, failed: 1, skipped: 2 },
  commit: "abc123",
  failures: ["Bundling failed"],
});
console.error(result.rendered); // original character reacting to actual facts
console.log(renderBuildSummary({ exitCode: 1 }, { format: "plain" }).rendered); // CI-friendly

The structured result exposes status, summary and rendered. summary includes copied facts and text. Counts are nonnegative safe integers; duration is finite milliseconds; labels/commit are bounded strings; up to twenty failure messages are accepted. Terminal control characters are removed from summary facts. Character mode accepts existing BroOptions; default moods react to passed/failed/unknown. Plain summary mode emits facts without character/personality decoration.

printf '%s' '{"exitCode":1,"tests":{"passed":42,"failed":1},"durationMs":1520}' | bro-say --summary --plain
node node_modules/@deployanyway/bro-say/examples/build-buddy.mjs src/index.js

--summary reads JSON stdin (256 KiB); --plain means a factual summary, --json returns the structured result. It rejects positional messages, presets, random selection and --box. Rendering exits 0 even when it describes failure; it is a presentation tool. The runnable build-buddy example executes an actual Node syntax check and preserves that command's exit status. Your build script must preserve its own status too.

Stable v1 contract

Node 22.13+ or Node 24. MIT licensed. CLI flags, structured fields, ESM/CommonJS exports and declarations are covered by tests and installed-package checks. Existing 0.4 APIs remain available except the explicitly documented doggo-log redaction/text-context changes. Future incompatible public API changes require a major release; callers should consume structured fields rather than parse jokes. Exact humorous wording and seeded catalog choices are version-specific. No telemetry, external API keys or network service is needed for core use.

Run npm test, npm run lint, npm run format:check, npm run coverage, npm run test:types and npm run verify:package from a source checkout. Runnable examples are shipped under examples/. The root demo is https://deployanyway.github.io/.

Message library and husky voices (0.4.0)

Twenty personalities now include Dallas, Benji, rubber-duck, on-call, code-review, minimalist, optimist and skeptic. Thirteen original characters and six themes remain. Your own message is never rewritten.

A library of 48 original message presets covers deployment, testing, debugging, review, coffee, celebration, husky and focus. Catalog arrays are independent copies; seed selection is repeatable within a package version.

npx @deployanyway/bro-say --preset husky --seed demo --mood dallas
npx @deployanyway/bro-say --preset review --seed demo --think
npx @deployanyway/bro-say --list-presets

import {
  broMessage,
  messageCategories,
  messagePresets,
  brosay,
} from "@deployanyway/bro-say";
const message = broMessage("debugging", { seed: "standup" });
console.log(brosay(message, { character: "duck", mood: "rubber-duck" }));
console.log(messageCategories(), messagePresets("husky"));

CLI --preset supplies a message instead of arguments or stdin. It rejects explicit message arguments; --seed can seed presets without --random. With both flags, the same seed also chooses unspecified artwork options. Custom character data remains available through the API; ANSI is terminal-specific.

Original terminal friends and developer personalities. Emotional support for production, without pretending to fix production.

npx @deployanyway/bro-say "Deploy anyway."

Version 0.4.0: requires Node 22.13+ or Node 24. See MIGRATION.md for changes from 0.2.0.

+----------------+
| BRO...         |
|                |
| Deploy anyway. |
+----------------+
   \
    \
       /\___/\
      / o   o \
      |   v   |
       \_===_/
       /| <> |\
      (_|____|_)
        /    \
       [_]  [_]
      [  LGTM  ]

Why?

Because production errors deserve emotional support. Your message stays yours; the mascot supplies questionable confidence.

Install

Install: npm install -g @deployanyway/[email protected]. Or run from source with Node 22.13+ or 24:

git clone --branch main https://github.com/DeployAnyway/bro-say.git
cd bro-say
npm ci
npm run build
node bin/cli.js "Deploy anyway."

30-second demo

Run these from the source checkout:

node bin/cli.js "Tests failed" --character husky --mood corporate
node bin/think.js "Maybe not on Friday." --theme neon --mood friday
echo "build failed" | node bin/cli.js --mood panic
node bin/cli.js "Hello 👋 こんにちは" --width 24
node bin/cli.js "Deploy anyway" --random --seed 42 --json

Say and think

import { brosay, brothink } from "@deployanyway/bro-say";
console.log(brosay("Production is down"));
console.log(brothink("Read the logs first.", { character: "duck" }));

Speech uses slash connectors; thoughts use circles. The installed package provides bro-say and bro-think; --think is equivalent.

Pipe anything into Bro

npm test 2>&1 | bro-say --mood panic
bro-say --character robot < build.log
error-translator ECONNREFUSED | bro-say --character husky

Arguments win over stdin; without arguments, piped or redirected input is read. No interactive message gets an actionable error. Stdin is limited to 256 KiB. Use your shell's pipefail policy to preserve upstream failures. Rendering exits 0; invalid input exits 2. Broken output pipes close quietly.

Characters

bro, bug, coffee, developer, duck, dumpster-fire, husky, intern, laptop, robot, rocket, server, wizard.

These 13 original printable ASCII drawings live in separate JSON files. The husky developer is our signature mascot. No cowsay assets or executable character definitions.

Moods

classic, hype, chill, panic, corporate, coach, senior-dev, intern, dramatic, sarcastic, motivational, friday.

Personas combine intros, labels and follow-up advice while preserving evidence. Corporate assigns an owner; panic asks for rollback; intern asks for a test; Friday checks on-call readiness. See generated captures below.

Themes

classic, minimal, neon, retro, hacker, corporate. Borders and ANSI palettes are independent of personas and characters. Neon uses Unicode box borders; the others use ASCII. API color defaults off; CLI color is off on noninteractive output. --color explicitly enables it; --no-color and NO_COLOR always win.

JavaScript API

import {
  renderBro,
  listCharacters,
  moods,
  listThemes,
  displayWidth,
} from "@deployanyway/bro-say";
const result = renderBro({
  text: "Hello 👋",
  character: "husky",
  mood: "chill",
  theme: "neon",
  mode: "think",
  width: 40,
  color: false,
});
console.log(result.rendered);
// result: text, character, mood, theme, mode, width, rendered
console.log(displayWidth("Hello 👋")); // 8

CommonJS: const { brosay } = require("@deployanyway/bro-say"). Browser: use @deployanyway/bro-say/browser through your bundler, or serve dist/browser.js directly. No network, telemetry or shell execution at runtime.

Seeded random selects unspecified character, mood and theme; explicit choices win. Same seed/options/catalog gives the same output. Catalog order may change between versions; archive the structured result for long-term reproduction.

TypeScript

Useful character, mood, theme and mode unions plus structured result types work in both module systems.

import { brosay, type BroOptions } from "@deployanyway/bro-say";
const options: BroOptions = { character: "husky", mood: "friday", width: 42 };
const output: string = brosay("Ship carefully.", options);

CLI reference

| Option | Behavior | | ------------------------------------------------ | ------------------------------------------------------- | | --think / bro-think | Thought connector | | --character, --mood, --theme | Independent selections | | --width 8..200 | Content columns; API default 48; CLI adapts to terminal | | --no-wrap | Preserve long lines | | --random --seed 42 | Repeatable choices; seed requires random | | --json | Structured result on stdout | | --color / --no-color | ANSI policy; NO_COLOR wins | | --list-characters / --list-moods / --list-themes | Catalogs; --list aliases moods | | --plain / --box | Original six mood layouts | | --help / --version | Concise help and version |

Use -- before messages starting with a dash. Catalog flags cannot be combined with rendering options.

Unicode support

string-width and wrap-ansi preserve combining marks, emoji clusters, CJK, newlines, blank lines and long words. Tabs become four spaces; CRLF is normalized. Unsafe terminal controls are removed; styling closes before borders.

Fonts/emulators may disagree on emoji and ambiguous widths. Width means content columns, excluding four border columns; artwork can be wider than a narrow bubble. API input is capped at 262144 UTF-16 code units and bubble output at 4096 lines. --no-wrap allows wide output.

Creating characters

console.log(
  brosay("Hello", {
    character: { name: "custom", art: ["[o_o]", " /| "] },
  }),
);

Custom characters need a slug and 1–20 printable ASCII lines of at most 64 characters. No code is evaluated. CONTRIBUTING explains adding one data file plus tests.

Browser demo

Run npm run build, serve the checkout with a static HTTP server, and open demo/. It uses the same renderer with live message, character, persona, theme, width, say/think and copy controls. Modern browsers need Intl.Segmenter and Unicode v-flag support. No backend or analytics.

Capabilities

| Capability | 0.4.0 | | --------------------------------------------- | -------------------------------- | | Speech / thought / stdin | Yes | | Original characters / personas / themes | 13 / 20 / 6 | | Grapheme and display-width wrapping | Yes, with terminal caveats above | | Seeded random / JSON / inert custom art | Yes | | JavaScript / types / ESM / CommonJS / browser | Yes | | NO_COLOR / installed archive checks | Yes |

Classic terminal tools inspired the quality benchmark. We make no blanket superiority claim; originality, JavaScript ergonomics and developer personas are this project's focus.

Contributing

Contribution guide · Conduct · Security · Roadmap · Migration. CI tests Node 22/24 on Linux and Node 24 on Windows/macOS, with coverage, types and archive installation. Releases are published after the versioned changes and required checks pass.

DeployAnyway ecosystem

error-translator explains errors; excuse-js supplies comic excuses; doggo-log adds personality to logs; ship-it-meter turns release evidence into a checklist. Each works independently.

Tools for developers who probably know better. Software nobody requested, built with questionable priorities, and shipped with absolute confidence!

License

MIT. Bundled third-party notices accompany the browser/CommonJS builds.

Generated terminal captures

Duck thinking

+----------------------+
| BRO...               |
|                      |
| Read the logs first. |
+----------------------+
   o
    o
         __
        (o )___
        /   __/
       /___/
       [QUACK]

Coffee

+-------------------------+
| BRO...                  |
|                         |
| Coffee is a dependency. |
+-------------------------+
   \
    \
         ~  ~
        .----.
        | CI |--.
        |    |  |
        |____|--'
        [REFILL]

Sarcastic robot

+--------------------------------------------+
| An ambitious interpretation of 'probably   |
| fine'.                                     |
|                                            |
| EVIDENCE RECEIVED                          |
|                                            |
| The deployment succeeded somehow.          |
|                                            |
| Excellent. Now let us ask the tests for a  |
| second opinion.                            |
+--------------------------------------------+
   \
    \
        [ READY ]
        .-------.
        | o   o |
        |  ===  |
        +-------+
       /|  []   |\
        |_______|
         []   []

Intern

+----------------------------------------------+
| I brought notes and exactly one sensible     |
| question.                                    |
|                                              |
| QUESTION FOR THE TEAM                        |
|                                              |
| Tests failed                                 |
|                                              |
| Could we add a test so future-me understands |
|  this too?                                   |
+----------------------------------------------+
   \
    \
        .----.
        |o  o|
        | ?? |
        \____/
        /|  |\
       [ NOTES ]
         |  |
        [_][_]