Skip to content

pixi

@data-xplorer/core/pixi — for writing custom renderers (US071 Step 7, ADR-016 A25).

Import this only from your renderers module, the one you hand the view as renderers={() => import("./my-renderers")}. That module, and PixiJS, are then loaded lazily, after the page. Build your views from the classes create(kit) hands you (kit.Container, kit.Graphics, …), and import from pixi.js only as types (import type): then PixiJS reaches the page by one lazy path, the package’s own. (A second runtime import of pixi.js, in your module, made Bun’s bundler emit a PixiJS chunk as one app’s page entry.) This entry adds only the contract’s types and an identity helper that checks a module against it. The package’s main and ./headless entries never reach this one (asserted by architecture.test.ts).

Re-exports ExplorerCluster


Re-exports ExplorerColour


Re-exports ExplorerEdge


Re-exports ExplorerEffect


Re-exports ExplorerEmphasis


Re-exports ExplorerItem


Re-exports ExplorerNode


Re-exports ExplorerOutline


Re-exports ExplorerPoint


Re-exports ExplorerRect


Re-exports ExplorerScene


Re-exports ExplorerShape


Re-exports ExplorerTexture


Re-exports ExplorerTruncation


Re-exports RenderNode


Re-exports windowed