caique

Changelog

Every release of caique, newest first, from its CHANGELOG.md — what changed and the pull request it came from.

2.1.1

Patch Changes

  • #1564 593c0b4 Thanks @ofri-peretz! - Measures with linegauge/v8, string-width 8.3.0's rules, which every incumbent these packages replace still resolves. Nothing a box, table, spinner, prompt, ink screen or help page draws changes: linegauge's root moved to string-width 9.0.0, and these stay on the measurement their wrap and slice cut by.
  • Updated dependencies [593c0b4]:
    • linegauge@2.2.0

2.1.0

Minor Changes

  • #1548 f190400 Thanks @ofri-peretz! - caique/clack follows @clack/prompts 1.9.0 (23 / 23, control 23 / 23). The spinner gains an accessible mode, turned on by accessible: true, by updateSettings({ accessible: true }) or by ACCESSIBLE in the environment. In that mode it prints plain appended lines a screen reader can follow, with no glyph, guide bar or escape:

    • the start;
    • still working: <message> every 30 s;
    • the ending, or Done, Canceled or the error message when the ending names none.

    caique/inquirer follows @inquirer/prompts 8.8.0 (228 / 228) and @inquirer/core 12.1.0 (47 / 47):

    • number calls validate with undefined when an optional prompt is left empty.
    • select takes an index only from plain digits, so 2e1 is not choice 20.
    • rawlist takes one only from digits with whitespace around them, so 2x is refused.
    • makeTheme keeps the default for a key set to undefined.

Patch Changes

  • Updated dependencies [f190400]:
    • linegauge@2.1.0

2.0.0

Major Changes

  • #1491 5054fb7 Thanks @ofri-peretz! - Requires Node 22.13 or later; Node 18 and 20 are end-of-life. engines.node is now >=22.13.0 (was ^20.19.0 || >=22.13.0), and Node 22.13, 24 and 26 are the versions tested. burgee migrate now warns when a project's engines.node admits a Node below 22.13.0, and its suggested fix is npm pkg set "engines.node=>=22.13.0".

Patch Changes

  • #1535 bad28b6 Thanks @ofri-peretz! - caique/clack paints its list hints and its required refusal when it draws them, and nests colours the same way on every Node.

    • The ↑/↓ to navigate hints under select and multiselect, and the refusal a required multi-selection shows ("Please select at least one option. Press space to select…"), were painted once, when the module loaded. They took whatever colour support the process had then, not the stream's when the prompt drew, so a prompt in a terminal could show them uncoloured. They are now painted per frame, as clack paints them.
    • On Node 22.13, an inner colour closing inside an outer one ended the outer one too: the yellow refusal lost its colour after space. Node 24 reopens the outer colour there, as picocolors does for clack; caique/clack now does the same on every Node it supports.

  • Updated dependencies [fca94b2, 5054fb7]:

    • linegauge@2.0.0
    • bellpull@2.0.0
    • closeout@2.0.0
    • paratext@2.0.0
    • roundel@2.0.0

1.6.3

Patch Changes

  • #1483 3e69fb2 Thanks @ofri-peretz! - The package manifest names its author and publishes with publishConfig { "access": "public", "provenance": true }. burgee's homepage is its landing page, https://burgee.interlace.tools. oxmutate gains keywords, so npm search finds it, and a sideEffects list (its CLI, its worker and its Vitest runner run on load), so a bundler can drop the rest. No code changes.
  • Updated dependencies [3e69fb2]:
    • bellpull@1.0.11
    • closeout@1.1.10
    • linegauge@1.2.1
    • paratext@1.0.13
    • roundel@1.3.2

1.6.2

Patch Changes

  • #1469 80fa4fb Thanks @ofri-peretz! - Two fixes.

    • An autocomplete search whose first match is disabled no longer overflows the stack. The cursor search stepped by Math.sign(0) from a disabled option, which is the same option again; it now searches forward, as upstream does, and lands on the next enabled match.
    • Line-mode select and multiselect read only an all-digits answer as a number. parseInt read 1 2 as choice 1, 2x as choice 2, and a label typed out, such as 3 apples, as choice 3. Those are now refused, and a label that starts with a digit is matched as that label.

  • Updated dependencies [80fa4fb]:

    • closeout@1.1.9

1.6.1

Patch Changes

  • #1337 9bf2624 Thanks @ofri-peretz! - caique/inquirer follows @inquirer/core 12.0.6 and caique/inquirer/prompts follows @inquirer/prompts 8.7.5. The first render waits a tick only when the input is a terminal, so an answer already piped into a non-TTY stdin before the prompt starts is read instead of dropped. password keeps the space after its message while the mask has nothing to draw, so the cursor sits past it. Their own suites grade them 46 / 46 and 222 / 222, level with the incumbents.

1.6.0

Minor Changes

  • #1316 d565864 Thanks @ofri-peretz! - promptFor asks for a command's missing option or positional, and refuses when nobody can answer (R1).

    • import { promptFor } from 'caique/prompt-for'. promptFor(command, 'name', { kind: 'text', message: 'Who?' }) wraps a command so its handler never sees a missing value. A person at a terminal is asked, on stderr, so the question never lands in the command's data. With no terminal, under CI, under a detected agent, under --json or in an --mcp tool call, it refuses with USAGE, naming how to pass the value: <name> for a positional, --dry-run for a dryRun option. A cancelled question is CANCELLED. burgee leaves with exit 2 or 4.
    • promptFor(command) resolves the prompt: a command already declares on its options or arguments. The command's shape is read structurally, and nothing in caique imports burgee.
    • The terminal is opened only to ask, handed to the host's exit path while it is open, and closed before the handler runs. Ctrl+C at the question gives the terminal back out of raw mode, on Linux, macOS and Windows.
    • A declared prompt is left out of the command's JSON, so --schema does not grow.
    • caique/clack's spinner({ style }) takes a spinner style as data, such as flagstaff's lookupSpinner(name) or a plugin's spinners entry. On a terminal its frames turn at its interval. Anywhere else its static line is printed in place of the first frame.
    • decide() and resolvePrompts() take a flag, which is how a refusal names an option when --<option> is not how it is passed.

1.5.2

Patch Changes

  • #1285 6570ff2 Thanks @ofri-peretz! - caique/inquirer follows @inquirer/core 12.0.5 and caique/inquirer/prompts follows @inquirer/prompts 8.7.4. A prompt cancelled or aborted before its first render never draws it and leaves no listener on the input. checkbox shows its loading state while an async validate runs and ignores every key until it answers. number reads a line of only whitespace as empty: the default, or a refusal under required. Their own suites grade them 45 / 45 and 221 / 221, level with the incumbents.

1.5.1

Patch Changes

  • #1258 e3b3a41 Thanks @ofri-peretz! - check reads a .json plugin file as data. It handed every file to import(), and Node refuses a .json module without an import attribute (ERR_IMPORT_ATTRIBUTE_MISSING), so a plugin written as JSON got Node's message and no verdict, from the host's own check and through burgee check, which runs it.

  • #1266 02e6f9f Thanks @ofri-peretz! - The family plugin schema (schema.json, identical in every plugin host) now describes formats, burgee's output-format key. This package reads nothing new, and a plugin carrying formats registers here as before.

  • #1252 efc994e Thanks @ofri-peretz! - Every benchmark figure in the README, a ratio, a byte count or a cold-start time, now links to the benchmarks page where it is measured.

  • Updated dependencies [e3b3a41, 02e6f9f, efc994e, efc994e]:

    • bellpull@1.0.10
    • closeout@1.1.8
    • linegauge@1.1.5
    • paratext@1.0.11
    • roundel@1.2.1

1.5.0

Minor Changes

  • #1201 70a86aa Thanks @ofri-peretz! - caique/inquirer/prompts now carries all ten of @inquirer/prompts' prompts: input, confirm, password, number, expand, rawlist, search and editor join select and checkbox, with their config and theme types. @inquirer/prompts 8.7.3's own suites pass 213 / 213, level with @inquirer/prompts itself (the eleven editor cases that answer through a mock of @inquirer/external-editor are excluded for both sides, D-20261011-inquirer-prompts-editor-mock). The subpath bundles to 44,683 B against the incumbent's 582,754 B. editor starts the user's editor through bellpull/cross-spawn, so caique now depends on bellpull.

1.4.5

Patch Changes

  • #1186 af24328 Thanks @ofri-peretz! - Published declarations now keep each doc comment's first paragraph, its code examples and its @param, @returns, @throws, @example, @deprecated, @default and @see tags, and drop the longer design notes below them, so the tarballs are smaller (burgee by 5.7% gzipped, bellpull and closeout by about a fifth). Types are unchanged, and hover text in an editor keeps its summary. burgee's README also names burgee/program-schema.json, the JSON Schema every --schema document validates against.
  • Updated dependencies [af24328, 122635d]:
    • closeout@1.1.6
    • linegauge@1.1.4
    • paratext@1.0.10
    • roundel@1.2.0

1.4.4

Patch Changes

  • #1160 0b381a0 Thanks @ofri-peretz! - Export ./package.json. require('<package>/package.json') threw ERR_PACKAGE_PATH_NOT_EXPORTED, which broke tools that read a dependency's manifest that way: bundlers, license scanners and version checks.
  • Updated dependencies [0b381a0]:
    • closeout@1.1.5
    • linegauge@1.1.3
    • paratext@1.0.9
    • roundel@1.1.3

1.4.3

Patch Changes

  • #1141 711ba15 Thanks @ofri-peretz! - caique/clack: a throw from the prompt's own code — a render, onKey or finalize that throws, on a key, on an abort, or on the first frame — now rejects the prompt's promise with that error, after turning raw mode off, removing the keypress listener and showing the cursor again. From a key it used to escape the keypress listener as an unhandledRejection, which kills a Node process by default, and left the prompt unsettled with raw mode on; from an abort it was an uncaught exception; from the first frame the promise rejected but left raw mode on and the keypress listener attached. A validator that throws is still a failed check, as before.

1.4.2

Patch Changes

  • #1130 c05c86e Thanks @ofri-peretz! - Every drop-in subpath now type-checks under moduleResolution: node10, and under module: commonjs with no resolution set, which is TypeScript's default there. import … from 'burgee/commander' used to fail with TS2307 in such a project, although require() of the same specifier worked. Each package now declares types and a typesVersions map, derived from exports, with one key per typed subpath pointing at the file exports already names. exports is unchanged, so node16, nodenext and bundler read exactly what they read before. controlroom/ink's declarations no longer name the untyped react-reconciler, which was TS7016 for consumers with skipLibCheck: false.
  • Updated dependencies [c05c86e]:
    • closeout@1.1.4
    • linegauge@1.1.2
    • paratext@1.0.8
    • roundel@1.1.2

1.4.1

Patch Changes

  • #1097 3f96896 Thanks @ofri-peretz! - caique/clack: a validator that throws, or returns a promise that rejects — a network check that fails, say — is now a failed check: the prompt shows the error's message (or the messages.error setting when it has none) and stays open, so the person can retry or cancel. It used to escape the keypress listener as an unhandledRejection, which kills a Node process by default; after an abort it escaped from a prompt that had already answered. @clack/core 1.5.1 lets it escape the same way.

1.4.0

Minor Changes

  • #1095 98a0004 Thanks @ofri-peretz! - A list prompt never outgrows the terminal. The raw select and multiselect draw a list longer than the screen as a window that follows the cursor, with ↑ N more and ↓ N more rows for what is outside it, so a repaint never climbs above the top row. The window is the new maxItems on a prompt spec, clack's name for it, and never more than the terminal's rows less three. renderList takes maxItems, and the terminal Writer reports rows, read live.

1.3.0

Minor Changes

  • #1037 50cc502 Thanks @ofri-peretz! - New entry point caique/inquirer/prompts: @inquirer/prompts' select and checkbox, with Separator and their config, theme and choice types, over caique/inquirer's prompt loop. Both are graded by their own suites in @inquirer/prompts 8.7.3, select's pagination suite included: 100 of those 100 cases pass, level with the real packages. Paging follows @inquirer/core's usePagination, multi-line choices and loop: false included. The other eight prompts are not built yet, so burgee migrate does not rewrite @inquirer/prompts imports. caique/inquirer is unchanged, and a program that imports it loads none of this.

1.2.1

Patch Changes

  • #1068 566b7d7 Thanks @ofri-peretz! - caique/clack: Ctrl-C or escape while an async validator is still out now cancels the prompt (it answers CANCEL_SYMBOL), where it used to be dropped. In raw mode Ctrl-C reaches the prompt as a byte, not a signal, so a validator that never answered left no way out. @clack/core drops the key too, but its readline interface then leaves raw mode, so a second Ctrl-C kills the process. Other keys still wait for the verdict.
  • Updated dependencies [4a62884]:
    • paratext@1.0.7

1.2.0

Minor Changes

  • #1060 52f6c71 Thanks @ofri-peretz! - --quiet reaches caique/clack's decoration. Every clack call's options take an optional runtime (roundel's policy Runtime, which is burgee's ctx.runtime). When it says quiet, spinner, tasks, intro, outro, note and log.message, info, step, success and warn write nothing, and the spinner arms no interval; their lifecycle methods still run. log.error and cancel still write, and prompts ignore quiet. A call without a runtime behaves exactly as before, and quiet is never read from argv or the environment. isCI() takes an optional runtime to read CI from.

    burgee's README shows the call under For agents: spinner({ runtime: ctx.runtime }).

Patch Changes

  • Updated dependencies [1797388]:
    • closeout@1.1.3

1.1.0

Minor Changes

  • #1045 c4fd9a3 Thanks @ofri-peretz! - caique's own chrome can speak the user's language. That covers the instruction under a list, a problem with an answer, the giving-up line, and the no-terminal and cancel refusals. A locale pack registered with register() carries translations under ids that begin caique., so one object can serve burgee's catalog too. The new caique/locale entry turns the runtime's locale into the translator: io.say = sayFor(runtime.locale). ask and resolvePrompts apply it. Neither reads the catalog itself, and caique never reads LANG. A refusal keeps its English message and fix, which a host may put in a machine envelope, and adds localised beside them. caique check renders a pack's messages, or refuses an unknown id, a stray placeholder or a missing plural form with E_PLUGIN_SCHEMA. With no say handed in, every byte is unchanged, and caique/clack and caique/inquirer keep their incumbents' English.

    burgee: the family plugin schema it publishes describes the locales key.

Patch Changes

  • #1045 c4fd9a3 Thanks @ofri-peretz! - The family plugin schema (schema.json, identical in every plugin host) now describes locales, burgee's locale-pack key. A plugin carrying locales validates against the shared schema as it does against burgee/locale-pack-schema.json, which lists every message id. This package reads nothing new, and a plugin carrying locales registers here as before.
  • Updated dependencies [c4fd9a3]:
    • closeout@1.1.2
    • linegauge@1.1.1
    • paratext@1.0.6
    • roundel@1.1.1

1.0.5

Patch Changes

  • #1012 49d8e94 Thanks @ofri-peretz! - @inquirer/prompts is now graded: its ten prompts' own suites (8.7.3) are vendored and run against caique/inquirer, with a control of 213 of 213 against the real packages. caique/inquirer passes 0 of them today, because it exports @inquirer/core's surface and none of the prompts yet, and burgee migrate reports @inquirer/prompts as a graded path that is not level, never rewriting it. The eleven @inquirer/editor cases are excluded by title: each answers the prompt through a mock of @inquirer/external-editor, which caique does not import.

    The oracle gains two host fields for it. suiteFiles lists a monorepo suite's files across several packages and vendors only those; defaultExport grades a suite that imports its prompt as a default against the named export a program migrates.

  • #1022 ecb0a00 Thanks @ofri-peretz! - The tarball no longer carries declaration files that no exports entry reaches. TypeScript could never open them, because a deep import is refused by exports. Every entry's types are unchanged. The ten packages drop 71 files and 118,312 bytes between them, burgee 35 files and 76,504 bytes, which takes its tarball from 251,814 to 225,278 bytes gzipped.

  • Updated dependencies [bfe4ab8, 1968eb4, 65afee5, bcc438a, ecb0a00]:

    • linegauge@1.1.0
    • paratext@1.0.5
    • roundel@1.1.0
    • closeout@1.1.1

1.0.4

Patch Changes

  • #938 9babb6d Thanks @ofri-peretz! - npm description and README: the description says what the package does, then its dependency fact in one of two wordings ("Zero dependencies." or "No dependency outside the burgee family."), then its drop-in paths. The README's family section states how the family is built — the leaves, one-way dependencies, nothing from outside the family, trusted publishing with provenance — and its table column is "Migrates from". No API, compatibility grade or benchmark changes.
  • Updated dependencies [9babb6d]:
    • closeout@1.0.4
    • linegauge@1.0.8
    • paratext@1.0.4
    • roundel@1.0.4

1.0.3

Patch Changes

  • #917 735f0f6 Thanks @ofri-peretz! - README: the opening paragraph says what the package does first. The drop-in path follows it as one line, naming the incumbent and npx burgee migrate, and every compatibility row and benchmark is unchanged.
  • Updated dependencies [735f0f6]:
    • closeout@1.0.3
    • linegauge@1.0.7
    • paratext@1.0.3
    • roundel@1.0.3

1.0.2

Patch Changes

1.0.1

Patch Changes

  • #886 d33ae03 Thanks @ofri-peretz! - The README and docs index say caique is 1.0, not "Released, pre-1.0.": it shipped 1.0.0 on 2026-10-08.

1.0.0

Major Changes

  • #851 446a691 Thanks @ofri-peretz! - caique 1.0.0. The spec is fully built, caique/clack (16 / 16) and caique/inquirer (41 / 41) pass their incumbents' own suites at the latest release, level with the incumbents, and coverage is 100% on all four measures (D-20261007-caique-controlroom-1-0-evidence). The published entries, the plugin schema.json and the caique bin become a semver contract. No API changed in this release.

Patch Changes

  • #857 d80b2d0 Thanks @ofri-peretz! - caique check refuses a widget whose static throws on its own sample. It used to print the throw as a row, then <name>: ok, and exit 0. Now each throwing widget is an E_NO_STATIC_PROJECTION refusal that names the widget and what it threw, with a fix, and the command exits 1 without printing ok.

  • #848 6ae533e Thanks @ofri-peretz! - The family schema.json describes what five values look like. contract is 1, and burgee refuses a plugin that declares none. A caique widget's static(spec) gets { kind, message, ...sample.done }. A seniority rank sits between the built-in layers at flag 0, environment 10, config file 20, package.json 30 and default 40. A burgee hook's filter is { command: RegExp }, now with command required, so the schema and the host refuse the same filters.

  • #857 d80b2d0 Thanks @ofri-peretz! - The family schema.json closes a bellpull resolver's when with additionalProperties: false, so the schema and bellpull's own validation refuse the same unknown keys.

  • #848 6ae533e Thanks @ofri-peretz! - Each README now shows a whole plugin as a default export, the command that checks it (from an install, and from a clone where dist/ has to be built first), and the report check prints when the plugin passes. caique says what a widget's static(spec) receives. seniority gives the rank for each slot between the built-in layers. bellpull says that {VAR} is the only substitution a path gets.

  • Updated dependencies [6ae533e, d80b2d0]:

    • closeout@1.0.1
    • linegauge@1.0.5
    • paratext@1.0.1
    • roundel@1.0.1

0.7.2

Patch Changes

0.7.1

Patch Changes

  • #810 a47209b Thanks @ofri-peretz! - caique/terminal: createIo()'s reader no longer drops lines that arrive before a question is asked. It listened for one line event per line() call, so printf 'x\ny\n' | cli lost both answers and ask() read the missing line as a cancellation. Lines are now queued from a single listener and handed out in order, before the end of the stream is.

  • #816 5230016 Thanks @ofri-peretz! - controlroom hosts plugins (R10): keymaps and panes register through controlroom/plugin's register() against the family schema, a screen takes either by name, and controlroom check <plugin-file> reports what a plugin contributes. The family schema every host ships gains the keymaps and panes definitions.

  • Updated dependencies [5230016, 5230016, 5230016]:

    • closeout@0.7.0
    • paratext@0.9.0
    • linegauge@1.0.4
    • roundel@0.6.3

0.7.0

Minor Changes

  • #801 81fc994 Thanks @ofri-peretz! - caique/editor: the line editor as a component a host drives (editor() returns initial, an onKey reducer and render), with multi-line entry, history, bracketed paste treated as text, and a completion menu the program feeds. Its commands are a caique/keys keymap (EDITOR_KEYS). Off a terminal, submissions(stdin) yields one entry per line and ends when the input does. The editing itself moved into a module caique/clack's prompts share, so there is one line editor in the package.

  • #801 81fc994 Thanks @ofri-peretz! - caique/keys: key presses decoded through node:readline's keypress events into one KeyPress shape, keymaps as plain data (match(), bindings()), and readKeys(), which takes raw mode once through closeout/cursor and throws E_NOT_A_TERMINAL with a fix instead of waiting when stdin is not a terminal. caique/raw's keyOf is rebuilt on the same decoder, and now reads the application-mode arrows (ESC O A) a terminal can send.

0.6.4

Patch Changes

  • Updated dependencies [b44f426, 6195b99]:
    • paratext@0.8.0
    • roundel@0.6.1

0.6.3

Patch Changes

  • #764 1817b62 Thanks @ofri-peretz! - caique/clack now grades 16 / 16 against @clack/prompts 1.8.1's own suite, level with clack itself at 16 / 16. It was 16 / 17. The pass count did not change. The denominator did: one case, guide.test.ts's no prompt renders a guide when withGuide is globally false, is now excluded by its exact title. It imports updateSettings from @clack/core and asserts that the prompts read that package's module state, so it grades @clack/core and not @clack/prompts (D-20260930-caique-clack-core-exclusion). The exclusion and its reason are on the compatibility page.

    Because the row is level, burgee migrate now rewrites @clack/prompts to caique/clack. It refuses a file that imports box, progress or taskLog, which caique/clack does not build, and leaves that file on clack. It does not rewrite @clack/core. So a migrated program that imports updateSettings from @clack/core is still changing clack's settings, and caique's prompts never read them. Import updateSettings from caique/clack instead.

  • Updated dependencies [6c2e9c5, 6c2e9c5]:

    • linegauge@1.0.1
    • paratext@0.7.5

0.6.2

Patch Changes

  • Updated dependencies [a115799]:
    • roundel@0.6.0

0.6.1

Patch Changes

  • #752 22e6dae Thanks @ofri-peretz! - A plugin that declares contract: 0 or a negative contract is now refused with E_PLUGIN_CONTRACT, as schema.json's minimum of 1 always said. These hosts checked only that a contract was not newer than the one they know, so 0 and below registered.
  • Updated dependencies [12bac9c, 22e6dae]:
    • paratext@0.7.4
    • closeout@0.6.1
    • roundel@0.5.6

0.6.0

Minor Changes

  • #638 e4c1f69 Thanks @ofri-peretz! - caique/clack now carries @clack/prompts' prompts, not only limitOptions: text, password, confirm, multiline, date, path, select, selectKey, multiselect, groupMultiselect, autocomplete and autocompleteMultiselect, with intro, outro, cancel, note, log, stream, spinner, tasks, group, the S_* glyphs, settings/updateSettings and isCancel, under clack's names and options. They run on caique's own keypress loop and reach nothing outside this repository. Graded by clack's own suite at 16 / 17 (was 14 / 17; the control is 17 / 17): the one case left imports updateSettings from @clack/core, which caique does not depend on (D-152). The spinner animates only on a terminal outside CI and prints each message once anywhere else. box, progress and taskLog are not built. burgee migrate reports the new grade and, since it is not level with the control, still does not rewrite @clack/prompts.

Patch Changes

  • #708 b52659f Thanks @ofri-peretz! - caique/clack: a prompt's raw mode goes through closeout/cursor's rawMode, as caique/raw already does. A prompt on a stream that was already raw no longer switches raw mode off when it ends, and raw mode it did turn on is also turned off on SIGINT and SIGTERM. caique/clack still grades 16 / 17 against clack's suite.

  • #726 2c631cb Thanks @ofri-peretz! - Two fixes in caique/clack, and paths no input could reach are removed. A prompt aborted while its validator was still running drew one more frame after it had closed and given the cursor back, so the frame landed under whatever the program wrote next; it now writes nothing once closed. date took a locale's field separator from its first literal, which in Pashto is the space after the era, so the fields read yyyy mm dd rather than yyyy-mm-dd; it now takes the literal after the first field, which is also right where the last literal is a suffix, as in Bulgarian's г.. caique/raw's askList, called directly with no choices, answered a multiselect with [''] after a space; it now answers []. The fallbacks removed from clack-core, clack-date, clack-prompts, clack-search, raw, binding and terminal are for values that are always there; behaviour is otherwise unchanged.

  • #727 b9de3f3 Thanks @ofri-peretz! - Four checks that could never change a result are removed from caique/inquirer; behaviour is unchanged. The screen's last line no longer falls back to an empty string (splitting a string always yields one), the loader no longer defaults a tick that useState(0) always sets, INQUIRER_KEYBINDINGS='' no longer has its own early return (it already parses to no bindings), and useMemo no longer asks whether a slot that holds a value was initialised.

  • #728 9a65722 Thanks @ofri-peretz! - caique/clack's spinner now ends on its errorMessage when the process exits with a failing code the program chose (2–127), as clack's does; before this every exit while spinning ended as a cancel, and errorMessage was never shown. A signal, and exit codes 0 and 1, still end as a cancel. Unreachable code is removed from the spinner and from caique check, whose never-called "replaces" helper is gone; behaviour is otherwise unchanged.

  • #680 7f59bc2 Thanks @ofri-peretz! - Raw mode is paired with its undo through closeout/cursor's rawMode, the way the cursor already was.

    • caique/raw: a list prompt on a stream that was already in raw mode — a prompt library's, or the program's own — no longer switches raw mode off when it ends; it used to call setRawMode(false) unconditionally and take the keyboard from its owner. Raw mode the prompt did turn on is now turned off on SIGINT and SIGTERM too, not only in the prompt's own finally. KeyStream gains an optional isRaw.
    • flagstaff/ora: stdin-discarder's raw mode goes through the same pairing. Behaviour is unchanged except that an already-raw stdin is no longer written to at all.

  • #677 8bc14e6 Thanks @ofri-peretz! - Measuring text against a terminal is linegauge's job, and four places did it by hand.

    • caique/raw: the repaint counted a frame's rows with split('\n') and ignored wrapping, so a choice whose hint was wider than the terminal left a stale copy of the question on screen after every keypress. It counts rows with linegauge's lineCount against the terminal's width, which Writer now carries as an optional columns (read through to the output stream by createIo). A writer without one is treated as never wrapping, as before.
    • burgee/testing: stripAnsi is linegauge's strip. The regex it used left private modes (ESC[?25l), the colon form of a truecolor SGR (ESC[38:2::255:0:0m) and OSC 8 hyperlinks in the text.
    • burgee help: descriptions and epilogues are folded by linegauge/wrap rather than a loop of help's own. A styled description now opens and closes its styles on each row instead of running its colour into the next row's indent, and a run of spaces at a break no longer leaves trailing whitespace. Lines the author indented are still kept verbatim, and a word wider than the row still overflows rather than breaking.
    • burgee config explain: the option column is padded in terminal columns, so a CJK option name no longer pushes its value two columns right of the others.

  • #674 e9f45d8 Thanks @ofri-peretz! - README: family header, badges, install, migrating, the family table.

    Every package README now opens the same way — lockup, tagline, one badge row in one order (npm version, downloads, Quality Gate, the package's own coverage, OpenSSF Scorecard, unpacked size, dependencies, types, Node, licence, npm provenance), a row of compatibility badges read from the graded baseline — and carries the same sections in the same order: Install for npm, pnpm, yarn and bun, Quick start, Migrating as a before/after diff, Compatibility, Benchmarks, For agents, API, and a generated table of the nine packages. Links are absolute, so they work on npm as well as GitHub.

  • #684 6c7b55a Thanks @ofri-peretz! - paratext/csi: the CSI half of ansi-escapes as a subpath of its own — cursor moves, erases, scrolling, the alternate screen and synchronized output, byte-exact with ansi-escapes 7.3.0. It is 2,700 bytes and, unlike the package root, registers no built-ins when imported.

    flagstaff/log-update, flagstaff/ora, caique/raw and caique/inquirer take their cursor sequences from it instead of carrying their own copies; caique now depends on paratext. Output is unchanged, with one spelling difference: caique/raw's repaint clears with ESC[J rather than the equivalent ESC[0J. caique/inquirer keeps @inquirer/ansi's answer of nothing for a zero-row move, where ansi-escapes' cursorUp(0) is ESC[0A.

  • #678 088cecc Thanks @ofri-peretz! - Whether anybody is there, whether to colour, and whether a tick can be drawn are roundel's questions, and three packages answered them by hand.

    • roundel/terminal (new subpath, 878 B, reaching nothing): interactive(rt) — a terminal on stdin, no CI, and no agent variable (CLAUDECODE, AI_AGENT, CURSOR_AGENT, CODEX_THREAD_ID, GEMINI_CLI, exported as AGENTS), with FORCE_TTY=1 as the override — and unicode(rt), is-unicode-supported 2.1.0's table over { env, platform }.
    • caique/decide now depends on roundel and asks interactive(). Behaviour change: under an agent that has a terminal — CLAUDECODE=1 and a TTY on stdin — a missing required value is refused with a usage error naming the flag (--x is required when nobody is there to answer) instead of prompting and hanging the agent. FORCE_TTY=1 now prompts even without a terminal on stdin, as it does for burgee.
    • caique/inquirer's tick and flagstaff/ora's log symbols and spinner fallback use roundel's unicode(). caique's copy was a four-condition subset: the Linux console (TERM=linux) now gets √ rather than ✔, and ConEmu/Cmder, Terminus, Alacritty, rxvt-unicode and JetBrains' terminal on Windows now get ✔, as figures draws them.
    • burgee help colour is roundel's colorLevel(rt) > 0. Behaviour changes: NO_COLOR now beats FORCE_COLOR; --no-color and --color=… on the command line are honoured; CLI_ACCESSIBLE turns help colour off; and a terminal that sets no TERM (Windows' conhost) gets plain help unless FORCE_COLOR, --color or COLORTERM asks for colour.
    • burgee/contrast rounds with roundel's round2; no output changes.
    • paratext: the supports-color fork behind paratext/terminal-link is unchanged, and now held to roundel's policy by a parity test everywhere their two incumbents agree.

  • Updated dependencies [6d8aadf, ff4159d, 5e635b0, ff4159d, 6ef8227, 7c77cd2, 6ef8227, 6ef8227, e9f45d8, 8a338ba, 6c7b55a, 620fc74, 088cecc, 4319563]:

    • closeout@0.6.0
    • linegauge@1.0.0
    • paratext@0.7.3
    • roundel@0.5.5

0.5.4

Patch Changes

  • #627 4a629a9 Thanks @ofri-peretz! - Lint with every published Interlace ESLint plugin, and fix what the upgrade surfaced.

    • caique: the inquirer theme merge skips __proto__, constructor and prototype keys, so a theme object cannot swap the merged object's prototype.
    • burgee: last-element reads use .at(-1).
    • burgee, closeout, flagstaff, roundel: helpers that capture nothing from their enclosing function move to module scope.
    • seniority: suppression comments name the no-dynamic-require rule that now reports the config loader's dynamic require.

    No public API or output changes.

  • Updated dependencies [4a629a9]:

    • closeout@0.5.4

0.5.3

Patch Changes

  • #604 0e7b1e8 Thanks @ofri-peretz! - Each README links to its migration guides under the docs link: "Migrating from: chalk", "ora · log-update · boxen · cli-table3", and so on. That puts a path from the npm page to the guide for the library you are replacing. No code changes.
  • Updated dependencies [0e7b1e8]:
    • linegauge@0.5.4
    • closeout@0.5.3

0.5.2

Patch Changes

  • #518 866b972 Thanks @ofri-peretz! - README weight lines now count every incumbent with a graded drop-in: terminal-link and term-img (paratext), exit-hook (closeout), @inquirer/core (caique).

  • #474 1955419 Thanks @ofri-peretz! - burgee plugins can hook two more stages. parse runs before the command is resolved: it receives argv and may return a replacement, which is how an alias plugin maps d to deploy. shutdown runs once as the program exits, whether the command succeeded or failed. The family schema.json shipped in every package now describes both stages.

  • Updated dependencies [866b972, 1955419, 1b002e0, 77ff1cb]:

    • closeout@0.5.2
    • linegauge@0.5.2

0.5.1

Patch Changes

  • #508 1aae1e2 Thanks @ofri-peretz! - <package> --help and --version answer instead of crashing. The bin took its first argument as the plugin file to import, so roundel --help failed with Cannot find module '…/--help' and exit 1. -h/--help now print usage and exit 0, -V/--version print the version and exit 0, and any other flag where the plugin file belongs is a usage error, exit 2.
  • Updated dependencies [1aae1e2]:
    • closeout@0.5.1
    • linegauge@0.5.1

0.5.0

Minor Changes

  • #507 b8e97dc Thanks @ofri-peretz! - Runs on Node 20 and 22, not just 24+: engines.node is now ^20.19.0 || >=22.13.0. Those are the first releases where require(esm) loads without a warning, so the CommonJS require() path keeps working. Every package's test suite runs on exactly 20.19.0 and 22.13.0, on Linux, macOS and Windows. caique's prompts no longer call Promise.withResolvers, which Node 20 doesn't have.

Patch Changes

  • #505 9800b43 Thanks @ofri-peretz! - Docs: the Benchmarks section's weight ceiling is re-measured against a fresh install of each incumbent's latest release (cosmiconfig 10.0.1, slice-ansi 9.0.1, which 7.0.0, dotenv 18.0.3, …) instead of the copies hoisted in this workspace, and names incumbents that were measured but left out of the ceiling as exactly that.
  • Updated dependencies [9800b43, b8e97dc]:
    • closeout@0.5.0
    • linegauge@0.5.0

0.4.3

Patch Changes

  • #494 f7f6d4b Thanks @ofri-peretz! - Each package's homepage and README docs link now point at its own documentation site, https://<package>.interlace.tools, instead of a page on burgee's site. The old burgee.interlace.tools/docs/packages/<package> URLs answer with a 301 to the new host, so nothing already linked breaks. closeout's README override example also resolves to the current release again (npm:closeout@^0.4; the 0.4.0 release left it at ^0.3).
  • Updated dependencies [f7f6d4b]:
    • linegauge@0.4.4
    • closeout@0.4.1

0.4.2

Patch Changes

  • Updated dependencies [69563d1, 2dc573f]:
    • closeout@0.4.0
    • linegauge@0.4.3

0.4.1

Patch Changes

  • #454 b4584e7 Thanks @ofri-peretz! - Every package's npm homepage now points at its page on the docs site, https://burgee.interlace.tools/docs/packages/<name>, and each README links it under the header. The keywords add what people and models search for: burgee gains cli-framework, argument-parser, subcommands, json-schema, mcp-server, model-context-protocol, ai-agent, llm, shell-completion, typescript, zero-dependency, commander-alternative and yargs-alternative; the other eight gain agent, ai-agent, non-tty, json and zero-dependency where the package does that — zero-dependency only on the six that install nothing at all.

    burgee's README gains a short FAQ (commander alternative, agent use, MCP, dependencies) and states the compatibility counts the oracle holds — 1,360 / 1,360 of commander's tests and 804 / 804 of yargs' — where it had said 1,215 and 1,185. caique's README no longer calls a released package pre-release.

  • #442 bdaf364 Thanks @ofri-peretz! - Every package now lists plugin, plugins and extensible in its npm keywords, because every package takes plugins through one shared contract.

    A plugin is a plain object, validated against the schema.json that ships in every package, and checked with the package's own check command. Each package reads its own key and ignores the rest, so one object can extend any subset of the family. The plugins page has a nine-layer example that every package's check accepts in CI.

  • #435 7888524 Thanks @ofri-peretz! - schema.json now describes every plugin host in the family.

    The one schema each package ships as its plugin contract used to cover only four hosts: roundel's tokens, flagstaff's glyphs, spinners, borders and components, paratext's capabilities, and linegauge's widths. Five hosts validated their keys in their own code, but the file an author (or a model) writes against said nothing about them. It now describes all of them:

    • bellpull resolvers, including the absolute-path rule on paths
    • caique widgets
    • closeout handlers, including the phases a plugin may use
    • seniority sources, including the rank bounds
    • burgee commands, hooks and enforce

    Where the schema can express a rule, it gives the same verdict as the host's own validator, and a test holds the two together. Function-valued fields (static, run, read, handler) are described and required, but not typed, because JSON Schema can't say "function".

    flagstaff now validates a plugin against only its own keys, not the whole family schema. It no longer refuses a plugin over another host's key, which lets one plugin object contribute to several hosts. Its entry points are also 4.7–5.9 KB lighter for it.

  • #445 dac303e Thanks @ofri-peretz! - Every package now declares sideEffects truthfully, so bundlers can drop what you don't import.

    Six packages declared nothing, so no bundler could drop any of their modules. A named import from the root now bundles to the same bytes as the same import from its subpath:

    importbeforeafter
    import { explain } from 'seniority'2,939 B1,067 B
    import { decide } from 'caique'1,235 B734 B
    import { strip } from 'linegauge'1,102 B940 B
    import { once } from 'closeout'353 B235 B

    flagstaff and roundel used to declare false, but each ships a check command whose file runs when loaded. Each now lists that file, which is the true statement. paratext also lists the two modules that register its built-in capabilities when they load.

  • #457 44edb2f Thanks @ofri-peretz! - flagstaff's npm description no longer says "Zero dependencies" (it takes four, all in-family); caique's README badge names both of its dependencies.

  • Updated dependencies [b4584e7, bdaf364, 7888524, dac303e]:

    • closeout@0.3.1
    • linegauge@0.4.1

0.4.0

Minor Changes

  • #421 db3c59e Thanks @ofri-peretz! - Every plugin host has a check command.

    npx linegauge check ./my-widths.mjs
npx burgee check ./my-plugin.mjs --json

    PRINCIPLES 7 asks three things of an extension surface: the plugin is data validated against one published schema, there is a check command that shows it every way it can be seen, and the bar is measured. The first was built in all nine hosts; the second existed in flagstaff alone. So an author writing a plugin for any other host found out what it did by shipping it into a program — and a surface nobody can check is a surface nobody outside this repository can write against.

    Each command validates, registers, and shows what the host does with the plugin, in the host's own terms: linegauge measures each code point before and after the override, paratext shows a capability's encode and its fallback, roundel each token and what it replaced, caique each widget's static projection rendered with its own sample. burgee's returns a document rather than printing one, so burgee check --json is the form an agent that just wrote a plugin reads.

    They share one contract with the author, held identically across all nine:

    • a readable report, contribution by contribution, with ok as the last line;
    • a refusal with a code from the family's vocabulary and a fix, exit 1;
    • E_NO_CONTRIBUTION for a plugin that contributes nothing to this host — the schema allows unknown keys so one object registers everywhere, which makes a misspelled key silent, and this is how that typo tells on itself;
    • exit 2 with no file.

    Each host also gains an eval case measuring the one-turn claim, proved to discriminate before it was committed: green against a correct plugin, red against the same plugin with one field broken.

Patch Changes

  • #430 4d1b2b3 Thanks @ofri-peretz! - check now reports every refusal with its code and its fix, wherever it was raised.

    Some plugin files register themselves on import: they call register() at the top of the module and export the result. Until now, when such a file was refused, the error was thrown inside check's import(), before the only try that turns a PluginError into E_PLUGIN_SCHEMA: … plus a fix: line. The author got the bare message on stderr, with no code and no fix. Now the whole of check runs inside that one handler, so every refusal comes out the same way on every host.

  • Updated dependencies [4d1b2b3, db3c59e, db3c59e]:

    • closeout@0.3.0
    • linegauge@0.4.0

0.3.1

Patch Changes

  • #398 ee35904 Thanks @ofri-peretz! - A __proto__ key in a caller's corpus stays a style.

    fromCliSpinners and fromCliBoxes built their maps by assigning map[key] = value over the caller's JSON. JSON can carry the key __proto__, and that assignment hands it to the prototype setter rather than defining a property: the entry vanished from the plugin and whatever it held became the fallback that every other lookupSpinner and lookupBorder inherited. Both now build with Object.fromEntries, which defines an own property for every key, and the returned map keeps Object.prototype.

    The registry's deepFrozen copy and caique's prompt binding write the same shape from a loop they cannot turn into an expression, and use Object.defineProperty instead.

    flagstaff/import is 80 bytes lighter for it — 838 B to 758 B — because two loops became two expressions.

0.3.0

Minor Changes

  • #381 8104eb9 Thanks @ofri-peretz! - caique/inquirer and caique/clack — two drop-in subpaths, and the first measured numbers either incumbent has given caique.

    caique/inquirer is @inquirer/core's surface over node:readline and node:async_hooks: createPrompt, useState, useEffect, useMemo, useRef, useKeypress, usePrefix, makeTheme, Separator, the eight key predicates and the five error classes. Graded 41 / 41, 100.0% against @inquirer/core 12.0.3's own suite, up from 0 / 41 — a suite that renders through a headless xterm and asserts the screen, so what passed is the prompt loop rather than a drawing. usePagination is not implemented and is named as a gap in .sdlc/intents/caique/design.md rather than shipped ungraded.

    caique/clack is limitOptions, which is the part of @clack/prompts that is a rule rather than a drawing. Graded 14 / 17, 82.4%, up from 0 / 606 — and the denominator moved for a reason published in full on the compatibility page: 289 of that suite's 444 assertions are toMatchSnapshot() across 17 of its 19 files, and those seventeen are subtracted as a declared subset, one named entry each. The three that remain unpassed are all of guide.test.ts and are a ceiling, not a shortfall: two want clack's twelve prompts drawn frame for frame, and the third asserts we read updateSettings out of @clack/core's own module state, which a package with no external dependencies cannot see.

    Both subpaths reach linegauge/wrap, and caique/inquirer also reaches closeout/exit-hook — both published from this repository, both declared, both budgeted in weight.test.ts. The package root is unchanged: nothing in either façade is reachable from caique itself.

Patch Changes

  • #373 a1f1d40 Thanks @ofri-peretz! - Stage 2's artifact is now spec.md, the name Anthropic's AI-Native SDLC playbook gives it, so the source comments and README sections that cite a package's own design document point at spec.md rather than design.md.

    No behaviour changes. The published tarballs do move, by two bytes per surviving reference — design.md is nine characters and spec.md is seven — so the four packages carrying a weight band were re-measured against it: linegauge 83,538 to 83,536; paratext 66,343 to 66,341; closeout 84,455 to 84,453; bellpull 86,113 to 86,107.

  • Updated dependencies [a1f1d40]:

    • closeout@0.2.1
    • linegauge@0.3.1

0.2.0

Minor Changes

  • #294 3f92a60 Thanks @ofri-peretz! - caique/plugin — a plugin may now ship a prompt kind caique does not have. register({ widgets }) keeps the widgets key and ignores every other layer's, so the same plugin object works on any subset of the family that is installed (plugin-contract R1, R5). A widget is the same shape a flagstaff component is — { static, frame?, sample? } — and one without static is refused with E_NO_STATIC_PROJECTION, the same code and the same fix shape.

    PromptKind is an open union (… | (string & {})). It was closed, which made a plugin's seventh kind a type error and would have turned hosting widgets into a breaking change written as an additive one; the six literals stay in an editor's completion list, which a bare string would have thrown away.

    Because the union is open, a kind nobody registered no longer falls through to a text prompt — projectionOf() refuses it with E_UNKNOWN_KIND, and the message names the kinds that are registered so the reader sees the typo rather than a text prompt where their widget should have been. The six built-ins are still drawn by caique and a plugin may not replace them: password guarantees that nothing writes back what it read, and a third party able to override it could defeat that from a config file.

    Also ships caique/schema.json, byte-identical to flagstaff's and roundel's (R2) — the specifier caique's own E_PLUGIN_SCHEMA fix names, so following the advice resolves.

Patch Changes

  • #326 88f7ba6 Thanks @ofri-peretz! - A Runtime seam on caique (PLAN 4.3, Y9).

    src/runtime.ts declares the slice of the world caique reads — env, stdin, stdout and the two isTTY flags — and processRuntime(), the one function in the package that names process. It is a function and not a constant, for the reason paratext's is: a runtime built at import freezes the environment as it was when the module graph loaded, which is before a test can say what it wants the world to look like.

    createIo() now takes no argument and builds over the real process, so a program gets the terminal it was started in without naming process itself; streamsOf(runtime) is the mapping for callers that already hold one. decide() is unchanged and still takes the narrower pair it reads, which is what the root export's Runtime continues to name.

    runtime.test.ts asserts the seam rather than documenting it: runtime.ts is the only non-test source in the package that reads the process, and processRuntime() returns two different answers across a change to the environment made after the import.

  • #332 3ea38c3 Thanks @ofri-peretz! - Restore the cursor when a prompt is killed, by taking the job from closeout.

    raw.ts hid the cursor and put it back on one path: the keypress loop, which sees Ctrl-C because raw mode delivers it as a byte rather than a signal. A SIGINT from a parent process, a SIGTERM, a crash or a process.exit() elsewhere in the program never reached that loop, and left the cursor invisible in the user's shell until they typed reset. Measured against the built dist/raw.js: hide 1, show 0, for SIGINT, SIGTERM and SIGHUP alike.

    askList() now hides through closeout.hideCursor(), which registers the restore in the same call, with closeout/exit-hook running it on the paths a keypress loop cannot see. The two escape sequences come from closeout/cursor as well, so caique no longer carries the family's third copy of them. The bytes on the wire are unchanged for a prompt that ends normally, and a prompt that ended unregisters, so exit writes nothing twice.

    caique therefore installs one package, closeout, which this repository publishes and which sits in the foundation tier below it. Nothing outside this repository is installed.

  • #339 f295630 Thanks @ofri-peretz! - schema.json constrains token names, because it was promising something no host honours.

    tokens was described as any name to a #rrggbb colour. roundel's validate() accepts ten semantic names — error, warn, ok, hint, muted, command, flag, value, heading, ground — and throws on everything else. So a plugin author doing exactly what their own E_PLUGIN_SCHEMA error tells them, comparing their object against roundel/schema.json, got a green from the schema and "accent" is not a token from register(). Measured 2026-09-16 with { accent: '#336699' }.

    The schema now carries propertyNames.enum, and scripts/plugin-contract-lock.test.ts pins the enum and the runtime set to each other from both sides, so neither can grow a name the other does not know.

    Every host ships a byte-identical copy of this file (plugin-schema-lock.test.ts asserts it), which is why nine packages are listed. Only the key roundel owns is constrained: describing widgets, handlers, sources, resolvers or commands in a file all eight hosts share is what made flagstaff start validating caique's key last time (PluginError: plugin.widgets.later: expected object, got boolean), and those stay in plugin-schema-lock's UNDESCRIBED list with that reason.

    linegauge is in the list for a different change: ceilings.json's R9 block now records the bar as D1's tree-inclusive ceiling — 83,538 against 170,342, a ratio of 0.4904 — and keeps the superseded get-east-asian-width bar beside it with the count of entries that cleared it.

  • Updated dependencies [c8acb28, fc640dd, 3f92a60, 3ea38c3, f295630]:

    • closeout@0.2.0

0.1.1

Patch Changes

  • #92 24e025d Thanks @ofri-peretz! - Lock caique's weight, per subpath, against clack.

    caique was the last published package in the family without a weight.test.ts — so the one package that talks to a person, and to an agent, was the one making an unmeasured claim.

    The whole package is 25,627 B and reaches no package at all, against @clack/prompts 1.8.0's 101,684 B across six. Deciding not to ask — the case an agent hits — costs 4,986 B and never loads the machinery of asking.

    Every entry now declares what it may import (nothing), what it may weigh, and what it must never reach; and an entry cannot be added without a budget.

0.1.0

Minor Changes

  • #71 e204772 Thanks @ofri-peretz! - Add caique/raw: arrow-key select and multiselect on a terminal that can take raw mode.

    askList() draws a moving highlight and repaints in place, and answers the same question ask() does with the same value — line mode stays the floor, this is decoration on top, and the suite proves the two agree by running one spec through both. keyOf() reads a keypress, canRender() says whether a runtime can take raw mode, and renderList() is one frame so the drawing is asserted rather than screenshotted.

    Ctrl-C cancels — in raw mode it arrives as a byte, not a signal — and the terminal is restored (raw mode off, cursor shown) whatever the answer.

    No dependency on flagstaff: a prompt has no spinner, and the repaint it needs is three escape sequences.

Patch Changes

  • #66 b43e1d3 Thanks @ofri-peretz! - ask() — the six prompt kinds in line mode, which is also the accessible rendering rather than a second implementation of it. A stream that ends is a cancellation, not an empty answer; invalid input is re-asked a bounded five times, never forever; projection(spec) gives the question without the conversation.

  • #66 b43e1d3 Thanks @ofri-peretz! - resolvePrompts() — the pass a framework calls from its preAction hook: walks a command's options in declaration order, asks only what has to be asked, and stops at the first refusal. One host-agnostic binding rather than one per host, so nothing in caique imports burgee.

  • #66 b43e1d3 Thanks @ofri-peretz! - decide() — the pure rule that decides whether a person can be asked at all: a value from any source wins, --json never prompts, --yes answers a confirm and only a confirm, and no terminal means an error naming the flag rather than a wait. All 256 combinations the design names are enumerated in the suite, not sampled.

  • #69 2da5883 Thanks @ofri-peretz! - createIo() — a reader and writer over real streams, so ask() can be used by a program and not only by a test. A password prompt is not echoed, and the muting lives in the one layer that knows what echo is.

FAQ

Short answers about caique — why it refused, --yes, --interactive, CI, closed stdin, passwords, raw mode, the drop-ins and CommonJS — each with where to read more.

On this page

2.1.1Patch Changes2.1.0Minor ChangesPatch Changes2.0.0Major ChangesPatch Changes1.6.3Patch Changes1.6.2Patch Changes1.6.1Patch Changes1.6.0Minor Changes1.5.2Patch Changes1.5.1Patch Changes1.5.0Minor Changes1.4.5Patch Changes1.4.4Patch Changes1.4.3Patch Changes1.4.2Patch Changes1.4.1Patch Changes1.4.0Minor Changes1.3.0Minor Changes1.2.1Patch Changes1.2.0Minor ChangesPatch Changes1.1.0Minor ChangesPatch Changes1.0.5Patch Changes1.0.4Patch Changes1.0.3Patch Changes1.0.2Patch Changes1.0.1Patch Changes1.0.0Major ChangesPatch Changes0.7.2Patch Changes0.7.1Patch Changes0.7.0Minor Changes0.6.4Patch Changes0.6.3Patch Changes0.6.2Patch Changes0.6.1Patch Changes0.6.0Minor ChangesPatch Changes0.5.4Patch Changes0.5.3Patch Changes0.5.2Patch Changes0.5.1Patch Changes0.5.0Minor ChangesPatch Changes0.4.3Patch Changes0.4.2Patch Changes0.4.1Patch Changes0.4.0Minor ChangesPatch Changes0.3.1Patch Changes0.3.0Minor ChangesPatch Changes0.2.0Minor ChangesPatch Changes0.1.1Patch Changes0.1.0Minor ChangesPatch Changes