zgx

zgx inspect

See and drive a running zgx Luau app: its tree, states and errors; clicks, typing and keys.

Read this once. It is everything you need to see and drive a zgx Luau app while it runs: what is on screen, what its state holds, what went wrong, and clicks, typing and keys, by the same names its tests use.

Start

zgx-run --inspect path/to/app/        # or ZGX_INSPECT_SOCKET=1 with any host that serves it
zgx inspect list                      # the apps serving devtools: pid and script
zgx inspect tree                      # what is on screen

With one app running, every command finds it; with several, add --app PID. Text answers by default (compact, a node a line); --json prints the answer as JSON ({"ok":true,"text":…,"data":…}, or {"ok":false,"error":…}) with exit code 0 on success, 1 on failure, 2 for bad usage and 3 when no app answers.

Edit on GitHub

Targets

One selector syntax for every command and for Rust tests: #id, "name", role:, @n, >>, row n, [n].

On this page

Start