Skip to main content

Browser

Browser is the canonical HST host name for Hosanna's shared Web DOM runtime. The legacy web CLI spelling remains a deprecated compatibility alias. Runtime identity remains PlatformId.Web or PlatformId.WebPwa, and shared code keeps the __WEB__ flag and HsPlatformTarget = 'web' contract.

Development Flow​

  1. Run npx hst run browser dev emulator or the project script that wraps it.
  2. Use fast refresh for views, styles, fragments, and data changes.
  3. Inspect runtime state with browser DevTools, Hosanna DevTools, and the MCP debugger.
  4. Validate keyboard, pointer, touch, remote-emulation, DPI, and design-resolution behavior.
  5. Build production web assets for hosted or embedded web delivery.

Runtime Notes​

  • Browser input adapters normalize keyboard, pointer, touch, and remote-emulation commands into the shared input model.
  • ?adapters= can limit active adapters for targeted tests.
  • The Browser target maps browser coordinates into Hosanna design coordinates so layout and hit testing stay platform-neutral.
  • AppConfig styles, fragments, data maps, and callbacks are loaded from the same app metadata used by other targets.

Browser and Installed App​

An installable Browser app keeps the Web DOM renderer and adds the web-pwa platform capability profile. In an installed window, Hosanna uses live viewport and DPR metrics, follows resize and physical-orientation changes, and exposes browser visibility and the full launch URL through the shared lifecycle service.

The framework does not choose product identity or presentation defaults. Hosanna Tools generates the generic install shell, while the host application owns its manifest identity, launch URL, icons, offline page, network policy, platform-web styling, and hosting configuration.

See Browser Progressive Web Apps (PWA) for the Vite integration, ownership boundary, caching policy, and release checks.

Release Checklist​

  • Run a production build.
  • Validate routes, asset paths, fonts, images, AppConfig loading, and environment configuration.
  • Test desktop browser, mobile browser, and embedded browser targets when those are part of the release.
  • For a PWA, validate installation, worker scope and updates, offline fallback, cache exclusions, resize, and rotation.
  • Use the MCP debugger and DevTools to inspect focus, view state, network behavior, and logs.

See Browser Expression, DPI, and Touch Input for Browser-specific launch parameters and input adapters.

Samsung Tizen and LG webOS consume the same renderer through their own compile targets. Use npx hst run tizen dev emulator or npx hst run webos dev emulator; changing only the device query parameter cannot select a vendor initializer.

Talk to us