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
- 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.
Curated by Skill Harbor — @pixijs's official breaking-change checklist for bringing a v7 codebase up to v8, meant to be worked top-down: imports → Application init → Graphics → Text → events → shaders/filters → cleanup. Covers the async `app.init()` (and `app.canvas` replacing `app.view`), the single `pixi.js` package with the full list of deprecated `@pixi/*` sub-packages that must never be imported, the new shape-then-fill Graphics API with the v7→v8 method rename table (`drawRect`→`rect`, `beginFill`→`fill`, `lineStyle`→`stroke`, ...), BaseTexture → TextureSource, the shader/uniform rework, constructor options objects, the removal of `DisplayObject`, `settings`/`utils` cleanup, the new Ticker signature and the events rewrite — plus custom-build setup with `skipExtensionImports` and the extensions that are never auto-imported (`pixi.js/math-extras`, `pixi.js/unsafe-eval`, ...). By @pixijs, listed here with credit to its creator. Honest caveats: upgrade-only reference — start new projects on v8 directly; assumes you can read the old v7 code you are porting; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
PixiJS v7 to v8 migration checklist is a free Muse skill that guides upgrading a v7 codebase to v8: async init, the single pixi.js package, shape-then-fill Graphics, BaseTexture removal, events rewrite and deprecated sub-packages, so the migration follows a checklist instead of guesswork and nothing important is left behind.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 83760c6Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/pixijs/pixijs-skills/83760c6f53462ca9cecd68055041f5a8c94758ce/skills/pixijs-migration-v8/SKILL.md Pinned version: install the code at commit 83760c6f53462ca9cecd68055041f5a8c94758ce exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 83760c6 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 11, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.