Separate the native implementation from the TypeScript bindings. Keep
core on
the public bindings and keep the current native artifact packages and
release
workflows.
packages/native owns the Zig source, tests, benches, and vendor updates.
The
package is private and unpublished for now Core still packages the
@opentui/core-* artifacts. build:native, test:native, and bench:native
still
work from core and delegate to native.
Expose a Zig import root and a no-JS hello example for proof of concept,
not a focus point, just a smoke test.
Allow examples to run under Node 26 with --experimental-ffi in addition to
Bun. Replace some Bun-specific APIs with standard Node equivalents, lazy-load
demos that still require Bun (WebGPU, sprites, shaders), and import Rapier via
its ESM subpath.
Extract examples, assets, install.sh, and the standalone build script
into a new workspace so they consume the public package surface
(@opentui/core, @opentui/three, @opentui/keymap) instead of reaching
into sibling internals. This makes examples a consumer of
the published API.
Drop the inherited browser export condition that prevented jimp from
resolving its node entry, which broke the standalone build.
## Summary
- Add complete Go bindings for OpenTUI with CGO integration
- Move opentui.h to centralized location for all language bindings
- Include working examples (basic and interactive console demo)
## Test plan
- [x] Go package builds successfully (`go build ./...`)
- [x] All tests pass (`go test -v`)
- [x] Basic example runs and displays output
- [x] Console demo runs with interactive features
- [x] Integration with main repository build system
Simon Klee