yawn/docs/packages/index.md

Package map

Install only the authoring and convenience layers your application needs. None of the addons is required by core's protocol.

@yawn/coreWorker commands, render-graph lifecycle, and shared SOA arrays. @yawn/render-graph-*Canonical AST plus JSO, fluent, and FXNode frontends. @yawn/gltf-importWorker-side glTF parsing directly into shared upload memory. @yawn/mesh-handlesGeneration-safe mesh, instance, camera, material, and picking facades. @yawn/default-pipelinesOptional scene WGSL and render/compute declarations. ExamplesEditable playgrounds that compose the public packages as an application would.

Dependency direction

Applications create core first, then pass the same YawnCore instance to addons. Addons use public commands and shared descriptors; core never imports an addon.

application ─▶ graph frontend ─▶ graph AST
     │                              │
     ├────▶ glTF / handles addons   │
     │             │                │
     └─────────────┴───────────────▶ core ─▶ render worker

This keeps scene policy outside the renderer. You can replace default pipelines, skip conventional handles, or author the AST directly without forking core.