Web workbench

This package is the generic JavaScript/Node browser workbench and composition layer.

Component implementations live in the concrete control packages under packages/web/*. This package owns the catalog client, application/form renderer, runtime event client, body/workbench shell, and their composition.

See ARCHITECTURE.md for the current package boundary map.

The workbench is a frontend client of a live UI runtime over HTTP. Application and form metadata are loaded from the backend catalog, while this package owns the browser composition and event flow.

Local dev

Start a compatible UI runtime separately and make it available at http://127.0.0.1:9000/ (or set WEB_RUNTIME_BASE to its URL).

A Nezam application can supervise both processes with:

nzm run web

That command starts the generated backend first, waits for its HTTP readiness, then starts this workbench and reports both URLs.

Then run the web workbench in another terminal:

cd packages/web/workbench
WEB_RUNTIME_BASE=http://127.0.0.1:9000/ npm start

npm run watch and npm run demo are aliases for the same Node development server. The published package contains the JavaScript/Node shell, its browser assets, and the local development server entrypoint. This server is not a production authentication or authorization boundary.

The shell binds to 127.0.0.1 on port 7100 by default. Override PORT if you want a different local port. The server proxies selected UI/runtime requests to WEB_RUNTIME_BASE; keep both services on trusted local or authenticated infrastructure.

To bind to a non-loopback interface, explicitly set both a host and a network token:

HOST=0.0.0.0 UI_WEB_NETWORK_TOKEN='use-a-long-random-token' npm start

Network requests must provide either Authorization: Bearer <token> or X-UI-ERP-Token: <token>. Do not expose this development server directly to the public internet; use a production gateway with authentication, authorization, TLS, origin policy, rate limits, and backend controls.