@octanejs/zag
v0.0.31
Published
Zag state-machine bindings for Octane, backed by the framework-agnostic @zag-js core packages.
Keywords
Readme
@octanejs/zag
Zag state-machine bindings for the Octane UI framework.
Installation
npm install @octanejs/zag
pnpm add @octanejs/zagThis package ports @zag-js/[email protected] onto Octane while reusing the
framework-agnostic @zag-js/core, @zag-js/store, @zag-js/types, and
@zag-js/utils packages unchanged. It is the runtime substrate for Octane
ports of component libraries built on Zag, including Ark UI and Chakra UI.
Change the framework adapter import while keeping machine definitions and
connect functions on their existing @zag-js/* packages:
// before
import { normalizeProps, useMachine } from '@zag-js/react';
// after
import { normalizeProps, useMachine } from '@octanejs/zag';import { normalizeProps, useMachine } from '@octanejs/zag';
import * as toggle from '@zag-js/toggle';
export function Toggle() @{
const service = useMachine(toggle.machine, { id: 'example' });
const api = toggle.connect(service, normalizeProps);
<button {...api.getRootProps()}>{api.pressed ? 'On' : 'Off'}</button>
}API
The public surface matches @zag-js/[email protected]:
useMachineruns a Zag machine with Octane hooks.normalizePropstypes Zag-generated host props for Octane JSX.Portalrenders intodocument.bodyor a supplied container and supports disabled and server-rendered in-place output.mergePropsis re-exported from@zag-js/core.useSyncExternalStoreis re-exported from Octane.
The adapter forwards Octane's compiler-assigned hook slots through every
composed hook and through Zag's indirect bindable and track callbacks.
Distinct machines and bindable context values therefore remain independent.
Verification
Behavioral tests cover transitions, bindable context, independent hook call
sites, multi-child portals, disabled portals, and server rendering. A
differential test runs the same machine through this package and
@zag-js/[email protected] and compares the state/context trace. Published source
and dependency checks ensure React is development-only.
Current scope and verification status are tracked in the generated
bindings status table, sourced from this
package's status.json.
