pixijs-migration-v8
This skill guides developers through upgrading PixiJS projects from version 7 to version 8, covering all breaking changes and API shifts. It provides a structured migration checklist and explains modern patterns for the fast WebGL-based 2D rendering engine. Perfect for teams maintaining graphics-heavy web applications.
pixijs-migration-v8 addresses the major API shifts between versions. Key breaking changes include the Graphics API moving from beginFill/endFill to a shape-then-fill pattern, deprecated @pixi/* sub-packages consolidating into a single pixi.js import, DisplayObject property removals, async App initialization, eventMode replacing the interactive property, and shader/uniform rework. The skill provides a complete checklist to systematically identify and fix each category of breakage in your codebase.
AI-generated summary based on this skill's SKILL.md
Install
pixijs/pixijs-skills/pixijs-migration-v8
git clone https://github.com/pixijs/pixijs-skills
cp -r pixijs-skills/skills/pixijs-migration-v8 ~/.claude/skills/pixijs-migration-v8Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What are the main pixijs breaking changes in v8?
pixijs-migration-v8 addresses the major API shifts between versions. Key breaking changes include the Graphics API moving from beginFill/endFill to a shape-then-fill pattern, deprecated @pixi/* sub-packages consolidating into a single pixi.js import, DisplayObject property removals, async App initialization, eventMode replacing the interactive property, and shader/uniform rework. The skill provides a complete checklist to systematically identify and fix each category of breakage in your codebase.
How do I upgrade pixi v7 to v8 in my project?
pixijs-migration-v8 guides you through a structured upgrade process. Start by updating your package.json to PixiJS v8, then work through the breaking changes checklist: migrate Graphics calls to the new shape-then-fill API, replace @pixi/* imports with pixi.js, update event handlers to use eventMode, fix Text constructor options, adapt shader uniforms, and handle async App initialization. The skill covers each migration step with concrete examples and common pitfalls to avoid.
What replaces pixi beginFill and endFill in v8?
pixijs-migration-v8 explains the new Graphics API. Instead of chaining beginFill().drawRect().endFill(), v8 uses a shape-then-fill pattern: you call a shape method like rect(), then apply fill() and stroke() separately. This provides clearer separation of concerns and more flexible styling. The skill shows side-by-side comparisons of v7 and v8 syntax, helping you quickly refactor your drawing code.
How do I migrate deprecated @pixi/* packages to pixi.js?
pixijs-migration-v8 covers package consolidation. In v7, you imported from @pixi/graphics, @pixi/text, @pixi/sprite, etc. In v8, all exports come from the single pixi.js package. Replace import statements like `import { Graphics } from '@pixi/graphics'` with `import { Graphics } from 'pixi.js'`. The skill lists the most commonly used sub-packages and their v8 equivalents, making the transition straightforward.
What shader and uniform changes does pixijs v8 require?
pixijs-migration-v8 addresses rendering pipeline updates. Shader uniforms, texture sources, and BaseTexture/TextureSource relationships have been reworked for better performance. The skill explains how to update uniform declarations, adapt TextureSource usage, and handle the new async initialization patterns. Event handler signatures and ticker callbacks have also changed; the skill shows the updated patterns for both.
What are common pixijs v8 migration mistakes to avoid?
pixijs-migration-v8 highlights frequent pitfalls: forgetting to await App.init() in async contexts, mixing old and new Graphics syntax in the same file, leaving @pixi/* imports after consolidation, not updating eventMode alongside removing interactive, and overlooking Text constructor option changes. The skill provides a checklist to catch these errors early, plus diagnostic techniques to fix broken code after upgrading.
SKILL.md
rendered from the published skill — quoted content, verbatim
This skill is a breaking-change checklist for bringing a v7 codebase up to v8. Work top-down through the categories; the list maps each v7 pattern to its v8 replacement.
Quick Start
Install the single package, then port in this order: imports → Application init → Graphics → Text → events → shaders/filters → cleanup.
const app = new Application();
await app.init({ width: 800, height: 600 });
document.body.appendChild(app.canvas);
const g = new Graphics()
.rect(0, 0, 100, 100)
.fill({ color: 0xff0000 })
.stroke({ width: 2, color: 0x000000 });
app.stage.addChild(g);
**Related
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/pixijs-migration-v8/SKILL.md