skills.rest
matthewharwood
matthewharwoodCOMMUNITY
Explore all skills by this author →
GitHub

pixijs-migration-v8

Migrate PixiJS v7 codebases to v8 with structured API rewrites.

1|Updated Apr 26, 2026
Search Tags:#typescript#textures#graphics#migration#shaders#pixijs#v7-to-v8
One-click install
npx skills add https://github.com/matthewharwood/dean-stack --skill pixijs-migration-v8-matthewharwood
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pixijs-migration-v8
Source: https://github.com/matthewharwood/dean-stack/tree/main/.claude/skills/pixijs-migration-v8
Command: npx skills add https://github.com/matthewharwood/dean-stack --skill pixijs-migration-v8-matthewharwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating a PixiJS v7 codebase to v8 can be error-prone due to widespread breaking changes, deprecated imports, and API rewrites; this Skill provides a structured migration guide.

Core Features & Use Cases

  • Guided, step-by-step migration for imports, constructors, and event handling to align with v8 APIs.
  • Scope coverage includes initialization, Graphics, Text, Textures, Shaders, and asset pipelines with concrete v7-to-v8 mappings.
  • Use Case: when upgrading a large PixiJS project, this Skill streamlines the process, mitigating regression risk and ensuring modern patterns.

Quick Start

Follow the migration checklist to upgrade your PixiJS v7 project to v8 by updating imports, constructors, and API usage.

Frequently Asked Questions about pixijs-migration-v8

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate PixiJS v7 to v8 without breaking my existing codebase?▼

PixiJS v8 migration involves replacing deprecated @pixi/* packages with single-package imports from pixi.js, converting constructors to options objects, and adopting eventMode to prevent regressions.

What are the breaking changes when upgrading PixiJS v7 to v8?▼

Breaking changes in the PixiJS v8 upgrade include Application.init changes, Graphics API rewrites, Texture modifications, and new uniform structures for Shaders across initialization and asset pipelines.

How do I update PixiJS Graphics and Textures for v8?▼

Updating PixiJS Graphics and Textures for v8 involves converting legacy constructor patterns to options objects and adopting new Texture and Graphics API structures to align with the v8 specification.

Can I still use @pixi/* sub-packages in PixiJS v8?▼

You cannot use deprecated @pixi/* sub-packages in PixiJS v8; the migration requires switching to single-package imports from the main pixi.js module to ensure compatibility.

Does PixiJS v8 migration affect event handling and initialization?▼

PixiJS v8 migration affects event handling and initialization by requiring the adoption of eventMode and transitioning to the Application.init method instead of legacy constructor patterns.

What is the best way to handle PixiJS shader and asset pipeline updates in v8?▼

The best way to handle PixiJS shader and asset pipeline updates in v8 is adopting new uniform structures and following structured v7-to-v8 mappings to ensure modern patterns and mitigate regression risk.

Related Skills

Explore More Software Engineering Skills→
pixijspixijs
302

pixijs-migration-v8

Identify and resolve PixiJS v7 to v8 migration issues with a structured checklist.

Official
Advanced
alexkaferalexkafer

pixijs-migration-v8

Generate a PixiJS v7-to-v8 migration checklist for breaking changes.

Community
Advanced
mikialexmikialex
74

shader-edsl-binding-and-typed-container

Bind typed GPU resource containers to shader EDSL and pass phases.

Community
Intermediate
encounterplusencounterplus
16

pixijs-migration-v8

Migrate PixiJS v7 code to v8 with replacement patterns for deprecated APIs.

Official
Advanced