Skip to content

Make DOM the default emulator and retain explicit WASM mode #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
puskuruk merged 2 commits into from
Sep 25, 2026
Merged

Make DOM the default emulator and retain explicit WASM mode #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c9a0724
Make DOM emulation the default and retain explicit WASM mode
puskuruk Sep 24, 2026
8332561
Prepare CLI 0.1.83 for DOM simulator 0.1.9
puskuruk Sep 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,3 +192,25 @@ built on it. The only GeaStack code under a different license is
the embedded board support (`targets` and `@geastack/chips`, GPL-3.0-only):
shipping closed-source firmware through those needs a commercial license.
Contact [contact@geastack.com](mailto:contact@geastack.com) for commercial terms, support and hosted builds.

## Browser development and emulation

`gea dev` (equivalently `gea dev --target web`) runs the Gea DOM/CSS app with
Vite HMR. `gea simulate` uses that same pipeline inside a device viewport and
opens the browser. Use `--no-open` to suppress opening, and `--width`, `--height`,
`--zoom`, and `--dpr` to configure the preview. DPR is a simulated Display API
value; it does not override the browser's pixel ratio.

The default for `simulate` changed from WASM to DOM. To retain the embedded
renderer and framebuffer workflow, use `gea simulate --renderer wasm`; this
explicit mode still requires Emscripten. Unknown renderer values are rejected.

`gea build --target web` emits HTML/JS/CSS into `.gea/build/web/site` (override
with `--out-dir`). The app's `index.html` is honored. Web-only Vite customization
belongs in `vite.web.config.ts`; new web apps scaffold this file. Existing
`vite.config.*` files remain dedicated to their previous build pipeline.

Compatible component edits and CSS changes update without reloading the page;
reactive state is preserved for compatible component edits. Incompatible edits
reload. Browser previews use simulated device APIs and browser layout; use the
WASM renderer or a physical device to validate embedded rendering.
Loading
Loading