Feature Request: Support for QuickJS engine to enable lightweight CLI usage on remote machines

[ild0tt0re]

Hi everyone,

I’ve been using rizetui and I love the interface and the way it handles TUI components. I’m looking for a way to run rizetui in environments where a full Node.js or Deno runtime is too heavy or simply not available.

Specifically, I’m interested in whether it would be possible to add support for the QuickJS engine.

The Use Case: Remote Machine Management via CLI

Many of us work on remote servers, edge devices, or minimal VPS instances where resource overhead is a major concern. When managing these machines via SSH, having a fast, low-footprint TUI is a game changer.

Why QuickJS?

• Minimal Footprint: QuickJS is incredibly lightweight (a few hundred KB) compared to Node.js.
• Zero Dependencies: It can be compiled into a single small binary, making it ideal for "copy-and-run" deployments on remote systems.
• Fast Startup: The near-instant startup time is perfect for CLI tools where you want to jump in and out of the UI quickly.

Proposed Idea

It would be amazing if rizetui could provide a compatibility layer or a specific build that targets QuickJS. This would allow us to:

1. Deploy rizetui as a standalone, tiny binary on any remote machine.
2. Run the TUI smoothly even on low-RAM devices (like Raspberry Pi Zero or micro-vps).
3. Avoid the "dependency hell" of installing a full JS runtime just to run a dashboard.

Alternative: txiki.js runtime based on QuickJS, but with Async IO built-in

I’m curious to hear the maintainers' thoughts on this. Is the codebase currently too dependent on Node-specific APIs (like fs or child_process), or could a polyfill/shim approach make QuickJS support viable?

Looking forward to your feedback!

[RtlZeroMemory]

Hello, I will have some free time next week to look into this idea and will update you in this thread. Thanks for suggestion