[GH-ISSUE #408] Move 3D module to separate @opentui/3d package #872

New issue

Open

opened 2026-03-14 08:53:21 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 08:53:21 +03:00

Owner

Originally created by @remorses on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/408

Installing @opentui/core pulls in 84 packages including three, planck, bun-webgpu, and rapier due to optionalDependencies.

Most users only need the core TUI functionality. Moving src/3d/ to a separate @opentui/3d package would keep the core package lightweight and let users opt-in to 3D features explicitly.

Originally created by @remorses on GitHub (Dec 11, 2025). Original GitHub issue: https://github.com/anomalyco/opentui/issues/408 Installing @opentui/core pulls in 84 packages including three, planck, bun-webgpu, and rapier due to optionalDependencies. Most users only need the core TUI functionality. Moving src/3d/ to a separate @opentui/3d package would keep the core package lightweight and let users opt-in to 3D features explicitly.

kerem added the

feature

core

labels

2026-03-14 08:53:21 +03:00

kerem commented

2026-03-14 08:53:32 +03:00

Author

Owner

@remorses commented on GitHub (Dec 11, 2025):

I can work on a PR if you agree

@remorses commented on GitHub (Dec 11, 2025): I can work on a PR if you agree

kerem commented

2026-03-14 08:53:37 +03:00

Author

Owner

@kommander commented on GitHub (Dec 11, 2025):

Would have to split up the examples then as well though as there are 3d examples. Which would mean either separate prebuilt example apps, which I don't like, or moving the examples into their own package as well and building from there. Needs pipeline adjustments then as well to publish these with the GitHub release. The examples wouldn't be a package though? So needs apps/examples parallel to packages?

Could get out of hand. Can we just make the dependencies dev dependencies for now? Or does it still install them all the time then?

@kommander commented on GitHub (Dec 11, 2025): Would have to split up the examples then as well though as there are 3d examples. Which would mean either separate prebuilt example apps, which I don't like, or moving the examples into their own package as well and building from there. Needs pipeline adjustments then as well to publish these with the GitHub release. The examples wouldn't be a package though? So needs `apps/examples` parallel to `packages`? Could get out of hand. Can we just make the dependencies dev dependencies for now? Or does it still install them all the time then?

kerem commented

2026-03-14 08:53:42 +03:00

Author

Owner

@remorses commented on GitHub (Dec 11, 2025):

Examples would remain where they are, we can just move the 3d code into another package and keep examples inside core folder.

These would import from @opentui/3d instead of relative imports, 3d would be installed as a workspace dev dependency

@remorses commented on GitHub (Dec 11, 2025): Examples would remain where they are, we can just move the 3d code into another package and keep examples inside core folder. These would import from @opentui/3d instead of relative imports, 3d would be installed as a workspace dev dependency

kerem commented

2026-03-14 08:53:47 +03:00

Author

Owner

@kommander commented on GitHub (Dec 11, 2025):

If that works and the prebuilt examples are working correctly I don't see why not. Little weird to have the examples in core with dependency on another package, perspectively would move them.

@kommander commented on GitHub (Dec 11, 2025): If that works and the prebuilt examples are working correctly I don't see why not. Little weird to have the examples in core with dependency on another package, perspectively would move them.