Compatibility

Nexa is backend-agnostic and cross-platform on the client. Here's what's verified today, and what isn't yet.

Backends

Any HTTP backend that answers JSON: load() makes a real GET against the URL you declare. Verified against a real PHP backend in Nexa's own reference project; it works the same with Go, Node, Python, Java, or whatever you already have — the contract is HTTP + JSON, not a proprietary SDK.

Browsers

Any modern browser with ES2022 support and native ES modules (import()/type="module"): current Chrome, Edge, Firefox and Safari. The client runtime doesn't use any framework — it's plain JavaScript, so the real requirement is the JS engine, not a library.

Platforms

Web (any static host or reverse proxy) out of the box. nexa add tauri generates a real desktop binary for Windows/macOS/Linux. nexa add capacitor generates an Android/iOS project — the Android build was verified end to end (a real APK built with Gradle); iOS requires Xcode, which can't be built or verified on Linux.

Building Nexa itself

The toolchain is written in Rust (the compiler) and TypeScript (the browser runtime). It was built and verified on Linux; Rust is cross-platform by design, so building on macOS should work the same way — that hasn't been verified yet in this round of phases. On Windows, the recommended path today is WSL.

Deployment

dist/ is 100% static HTML/CSS/JS — any static host (Nginx, GitHub Pages, Cloudflare Pages, S3, whatever) serves it as is. nexa add nginx generates a real deploy/nginx.conf, with safe cache-busting for hashed files, if your host is a server you run yourself. This very site, in fact, is deployed on GitHub Pages — the same dist/, no nginx involved.