@noxigui/noxi.js
v0.2.1
Published
`@noxigui/noxi.js` bundles the NoxiGUI runtime with the PIXI renderer so applications can parse markup, bind view models, and render interfaces with a single dependency. The package is published as native ESM and exposes both `module` and `default` entry
Readme
@noxigui/noxi.js
@noxigui/noxi.js bundles the NoxiGUI runtime with the PIXI renderer so applications can parse markup, bind view models, and render interfaces with a single dependency. The package is published as native ESM and exposes both module and default entry points so bundlers can resolve it via import statements.
Installation
pnpm add @noxigui/noxi.js
# or
npm install @noxigui/noxi.js
yarn add @noxigui/noxi.jsUsage
import Noxi, { createGui, createPixiRenderer, ObservableProperty } from '@noxigui/noxi.js'
const xml = `<TextBlock Text="{Binding Greeting}"/>`
const viewModel = { Greeting: new ObservableProperty('Hello!') }
// Default export exposes the PIXI renderer through Noxi.gui.create.
const gui = Noxi.gui.create(xml)
// You can pass an explicit renderer instance when needed.
const pixiRenderer = createPixiRenderer({ background: 0x000000 })
const customGui = createGui(xml, pixiRenderer)
customGui.bind(viewModel)The package re-exports the runtime API (ObservableProperty, ObservableCollection, layout primitives, and more) so existing guides in docs/ apply without additional imports.
Local development
Rebuild the distribution before publishing changes:
pnpm install
pnpm -F @noxigui/noxi.js buildAfter compiling dist/, use the repository-level script to release updated packages in dependency order:
pnpm run publish-packagesThe publish script expects package versions to be bumped and the artifacts in dist/ to be current. It keeps running even when
one publish fails and prints a table summarizing which package versions published successfully along with any error messages.
