executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
ionic-app-upgradesGuides the agent through upgrading an Ionic Framework app to a newer major version. Supports upgrades from Ionic 4 through 8, including multi-version jumps. Covers framework-specific migration steps for Angular, React, and Vue, component breaking changes, CSS variable updates, and browser support changes. Do not use for Capacitor version upgrades (use capac…
Independent GitHub snapshot · Automated classification · Original documentation governs
Upgrade an Ionic Framework app to a newer major version (4 to 5, 5 to 6, 6 to 7, or 7 to 8).
| Target Version | Angular | React | Vue |
|---|---|---|---|
| 5 | 8.2+ | 16+ | N/A |
| 6 | 12+ | 17+ | 3.0.6+ |
| 7 | 14+ | 17+ | 3.0.6+ |
| 8 | 16+ | 17+ | 3.0.6+ |
Read @ionic/angular, @ionic/react, or @ionic/vue version from package.json (dependencies or devDependencies). Determine the current major version and which framework is in use (Angular, React, Vue, or Core/Standalone).
Ask the user for the target version. Default to the latest (8) if not specified.
For each major version jump between the current and target version, apply the corresponding upgrade guide sequentially:
| Current to Target | Reference |
|---|---|
| 4 to 5 | references/upgrade-v4-to-v5.md |
| 5 to 6 | references/upgrade-v5-to-v6.md |
| 6 to 7 | references/upgrade-v6-to-v7.md |
| 7 to 8 | references/upgrade-v7-to-v8.md |
For multi-version jumps (e.g., 5 to 8), apply each upgrade in order:
references/upgrade-v5-to-v6.mdnpm run build), fix any errors, and verify the app runsreferences/upgrade-v6-to-v7.mdnpm run build), fix any errors, and verify the app runsreferences/upgrade-v7-to-v8.mdnpm run build), fix any errors, and verify the app runsDo not skip intermediate versions.
After completing all upgrade steps:
npm run build
If the project uses Capacitor, also run:
npx cap sync
npm run build fails after an upgrade step, check the compiler errors. Most errors are caused by removed component properties, renamed CSS variables, or changed event handler signatures documented in the reference files.transformIgnorePatterns configuration — Ionic 6+ ships as ES Modules and requires Babel/Jest configuration updates.capacitor-app-upgrades skill.capacitor-app-upgrades — If Capacitor also needs upgrading alongside Ionic, use this skill for the Capacitor-specific upgrade steps.ionic-app-development — General Ionic development guidance.capacitor-plugins — For installing or reconfiguring plugins after the app upgrade.