opentui

Scaffold a project with bunx create-tui -t react my-app (or -t solid / -t core), then run it with bun run. The template flag must come before the directory name, and the target directory must not already exist.

Use Core for maximum control, smallest bundle, or when building libraries on top of OpenTUI. Use React if your team knows React patterns, and Solid when you want fine-grained signal-based reactivity with optimal re-rendering.

For simple shortcuts, use the useKeyboard hook in React or Solid, or renderer.keyInput events in Core. For layered bindings, leader keys, sequences like dd, and ex-style commands, use the separate @opentui/keymap package.

Bun is the reference runtime, with Zig used for native builds. Node.js 26.3.0 is supported for the native renderer when launched with --experimental-ffi, and @opentui/keymap imports in Node without any FFI.

Use createTestRenderer from @opentui/core/testing for headless rendering, or testRender from @opentui/react/test-utils or @opentui/solid. Capture frames with captureCharFrame() for assertions or snapshots, and always destroy the renderer after each test.

Text styling in React and Solid requires nested modifier elements like <strong>, <em>, or <span fg="red"> inside <text>, not style props. Passing styling props directly to text content does not apply attributes.