← Products

Frontend
⚙ Needs: an existing PixiJS v7 codebase to upgrade; nothing e…

PixiJS v7 to v8 migration checklist

Upgrade a v7 codebase to v8 — async init, single pixi.js package, shape-then-fill Graphics, BaseTexture removal, events rewrite, deprecated sub-packages

At a glance
What
Upgrade a v7 codebase to v8 — async init, single pixi.js package, shape-then-fill Graphics, BaseTexture removal, events rewrite, deprecated sub-packages
Cost
Free
Needs
an existing PixiJS v7 codebase to upgrade; nothing else — the skill is a migration checklist plus code patterns, no accounts or keys required
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @pixijs
⌁

Install

Prerequisites: an existing PixiJS v7 codebase to upgrade; nothing else — the skill is a migration checklist plus code patterns, no accounts or keys required Install "PixiJS v7 to v8 migration checklist" for me. It gives the agent @pixijs's official v7→v8 breaking-change checklist, worked top-down: async app.init, the single pixi.js package with the full deprecated @pixi/* list, the shape-then-fill Graphics API with the v7→v8 rename table, BaseTexture → TextureSource, shader/uniform rework, constructor options objects, DisplayObject removal, settings/utils cleanup, the new Ticker signature, the events rewrite, and custom-build setup with skipExtensionImports. MIT-licensed. Repository: https://github.com/pixijs/pixijs-skills/blob/main/skills/pixijs-migration-v8/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "pixijs-migration-v8". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the v7 codebase to port, module by module, following the checklist order). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.