What problem does it solve?
PixiJS beginners often struggle to understand where rendering actually happens—how the renderer backend is chosen, how the render loop drives per-frame work, and how PixiJS adapts to different runtime environments.
Core Features & Use Cases
- Renderer backend selection: Decide between WebGLRenderer, WebGPURenderer, and CanvasRenderer using PixiJS environment detection and auto-selection via Application.init options.
- Render pipeline and frame execution: Follow how renderer.render() participates in the ticker-driven render loop, including traversal, transforms, culling, and GPU command submission.
- Environment adaptation: Use DOMAdapter concepts to run in browser, Web Worker, or constrained/SSR contexts by selecting the correct adapter before Application.init.
Use case: You’re integrating PixiJS into a React/TypeScript app and need to reliably run per-frame animation, ensure you pick the best available backend (WebGPU vs WebGL), and avoid common init-order bugs that lead to undefined renderer fields.
Quick Start
Use the pixijs-core-concepts skill to decide which renderer backend will run, then implement per-frame animation via app.ticker and query app.renderer.name after init resolves.