pixi-vn-migration

Migrates @drincs/pixi-vn projects across versions using documented breaking-change mappings.

145|9|Updated Feb 14, 2024
One-click install
npx skills add https://github.com/DRincs-Productions/pixi-vn --skill pixi-vn-migration-drincs-productions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pixi-vn-migration
Source: https://github.com/DRincs-Productions/pixi-vn/tree/main/skills/migration
Command: npx skills add https://github.com/DRincs-Productions/pixi-vn --skill pixi-vn-migration-drincs-productions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading the @drincs/pixi-vn game engine often breaks existing code because APIs are renamed, reorganized into namespaces, or removed between versions. This Skill provides a complete version-by-version migration guide so developers can update projects without hunting through changelogs. ## Core Features & Use Cases - Breaking Change Catalog: Covers every breaking change from v0.10.x through v1.9.0 with before/after TypeScript code snippets. - Namespace Migration Maps: Documents the reorganization of canvas, sound, storage, and narration manager methods into namespaced sub-APIs like canvas.tickers and narration.labels. - Targeted Upgrade Paths: Walks forward only through the version boundaries a project actually crosses, based on the installed version in package.json. - Use Case: A developer upgrades from v1.7.x to v1.9.0 and hits a type error on sound.channels; this Skill shows the array moved to sound.channels.values and provides the exact replacement code. ## Quick Start Ask the AI to upgrade this project's @drincs/pixi-vn dependency to the latest version and fix any resulting errors using the migration guide.

Frequently Asked Questions about pixi-vn-migration

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

FAQPage Schema
How do I upgrade @drincs/pixi-vn to the latest version?

Check the installed version in package.json, then walk forward through only the version sections between it and the target. Each section lists breaking changes with before/after code, so you apply only the migrations relevant to your version jump.

How do I fix sound.channels type errors after upgrading pixi-vn?

In v1.9.0, sound.channels changed from an array to an object, and the array moved to sound.channels.values. Replace sound.channels.map(...) with sound.channels.values.map(...) to resolve the type error.

Does the pixi-vn migration guide cover the nqtr and pixi-vn-ink packages?

No, this guide only covers the core @drincs/pixi-vn package. The official docs at pixi-vn.com/faq/migration cover the separate nqtr and pixi-vn-ink packages.

Why did Game.onError stop working after upgrading pixi-vn?

The singular Game.onError handler was removed in v1.9.0 after being deprecated since v1.6.0. Use Game.addOnError instead, which supports multiple stacked handlers and drops the type argument from the callback.

Are old flat canvas and narration methods removed in pixi-vn v1.9.0?

Most old flat methods still work and forward to their namespaced replacements, marked as deprecated but not removed. Only sound.channels and the narration.choices getter break immediately because their types changed.