Terminal image

Render terminal images when the capability profile permits them and deterministic text fallbacks everywhere else.

Overview

Render terminal images when the capability profile permits them and deterministic text fallbacks everywhere else.

Loading executable example…

Components and subcomponents

API	Signature	Description
`TerminalImage`	`function TerminalImage`	Public function TerminalImage.
`renderTerminalImage`	`function renderTerminalImage`	Public function renderTerminalImage.

Interaction

Image output follows terminal capability detection and explicit dimensions.

API and events

No events are emitted.

Every interactive component publishes semantic roles, labels, state, and focus identity through the renderer's SemanticRegistry. Callback failures flow to the owning application's error boundary.

Documentation flow diagram. props and runtime state; semantic registration; focus and input routing; callback or state update; rerender; S0 leads to S1; S1 leads to S2; S2 leads to S3 — **Documentation flow diagram.** props and runtime state; semantic registration; focus and input routing; callback or state update; rerender; S0 leads to S1; S1 leads to S2; S2 leads to S3

Example

import type { ComponentProps } from "react";
import { TerminalImage } from "@mwillbanks/tuil-ink";

export function Example(props: ComponentProps<typeof TerminalImage>) {
  return <TerminalImage {...props} />;
}

Registry-installed components are source-owned: customize the generated file in your application, and use the package reference for the shared runtime contracts.