@xemahq/app-web
v0.6.2
Published
Layer 1 SDK: the coded-frontend authoring surface for a Xema app (D19). `defineWebApp({ pages })` is a thin composition over @xemahq/ui-kernel's `defineWebBiome`/host loader — an ejected app's frontend registers the same way a first-party web biome does,
Readme
@xemahq/app-web
This package belongs to Layer 1 — a thin SDK composition over the Layer-1
@xemahq/ui-kernel and @xemahq/app-ui, with no dependency on any Xema service
or higher-layer package.
@xemahq/app-web is the coded-frontend authoring surface for a Xema app
(D19). defineWebApp({ pages }) composes @xemahq/ui-kernel's defineWebBiome
and the host loader, so an ejected app's frontend registers exactly the way a
first-party web biome does — one default-exported factory the host mounts, no
forked loader or registry. It also re-exports AppShell from @xemahq/app-ui.
Usage
import { defineWebApp, AppShell } from '@xemahq/app-web';
import HomePage from './pages/Home';
export default defineWebApp({
id: 'my-app',
displayName: 'My App',
pages: [
{ slug: 'home', label: 'Home', load: () => import('./pages/Home') },
],
});Each page carries the full kernel route expressiveness (scope, access,
chrome), including public + chromeless surfaces.
Prerequisite status
The plan-of-record flagged a kernel widening (a public/chromeless route scope on
defineWebBiome) as this package's prerequisite. That widening is already
present in @xemahq/ui-kernel (RouteScope/RouteAccess include public,
PageChrome includes none), so defineWebApp composes the current enums
unchanged — no kernel enum change is required or performed.
Exports
.—defineWebApp,DefineWebAppOptions,WebAppPage, andAppShell/AppShellProps(re-exported from@xemahq/app-ui).
