GeaStack’s public examples repository presents a small app gallery for a framework the publisher calls GeaStack. The README says the collection is used by the simulator, embedded targets, GeaOS, Apple targets, and a VS Code/Cursor extension, and that most examples are TSX apps targeting web, ESP32, and/or GeaOS.
Placed after the gallery overview because the repository preview directly identifies GeaStack’s example apps and their use across the simulator and targets.
The clearest technical detail is the build contract. Each buildable example is expected to have a `package.json` with a `gea` manifest containing an app ID, entry point, runtime, and target compatibility. The README says that manifest is consumed by the simulator, embedded board scripts, GeaOS, Apple targets, and the IDE extension, so target support is declared per app rather than implied for the whole collection.
The repository also shows how the publisher expects examples to be checked. It documents running `npm install`, `npm run check`, and `npm run build` inside an app folder, with tests available for some layout or device setups. It separately points developers to a simulator repository and to `GEA_APPS_ROOT` or `--app-dir` when running the web loop.
The important limitation is scope. The supplied source does not establish a complete list of supported TypeScript or JavaScript features, nor does it show a native binary produced for every target. It also describes some targets, such as web, without proving that they are native in the same sense as a device or operating-system target. The evidence supports a practical conclusion: this is a focused example gallery with explicit target manifests, not enough documentation to guarantee portable behavior across radically different runtimes.