Browser runtime

HyperToken's shared browser tooling turns a Node-oriented entry point into an ESM browser bundle. It supplies aliases for the Node APIs used by the Engine, inlines Automerge's browser WASM entry point, and leaves static hosting to the application.

The supported path is the shared builder in core/browser/build.js. Browser applications still need a suitable WebSocket endpoint, browser storage policy, and deployment configuration. The build tooling does not provide a server, service-worker lifecycle, or application authentication.