[GH-ISSUE #489] Language bindings should live in separate repositories #894

Open
opened 2026-03-14 08:58:05 +03:00 by kerem · 0 comments
Owner

Originally created by @msmps on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/489

Policy update

Going forward, all new language bindings should be maintained as separate standalone repositories.

Why this policy exists:

  • Maintaining language bindings in the monorepo creates a maintenance bottleneck
  • Each binding requires reimplementing large portions of the TypeScript API
  • When maintainers become busy or move on, bindings fall behind and accumulate technical debt

Examples of binding requests:

  • #217 - Python bindings
  • #107 - Svelte reconciler
  • #236 - .NET bindings

The main opentui monorepo will officially support only: @opentui/core, @opentui/react, and @opentui/solid.

Originally created by @msmps on GitHub (Jan 7, 2026). Original GitHub issue: https://github.com/anomalyco/opentui/issues/489 ## Policy update Going forward, all new language bindings should be maintained as separate standalone repositories. ## Why this policy exists: - Maintaining language bindings in the monorepo creates a maintenance bottleneck - Each binding requires reimplementing large portions of the TypeScript API - When maintainers become busy or move on, bindings fall behind and accumulate technical debt ## Examples of binding requests: - #217 - Python bindings - #107 - Svelte reconciler - #236 - .NET bindings The main opentui monorepo will officially support only: **@opentui/core, @opentui/react, and @opentui/solid.**
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/opentui#894
No description provided.