Ionic App Upgrade
Upgrade an Ionic Framework app to a newer major version (4 to 5, 5 to 6, 6 to 7, or 7 to 8).
Prerequisites
| 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+ |
Procedures
Step 1: Detect Current Version
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.
Step 2: Execute Upgrade
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:
- Read and apply
references/upgrade-v5-to-v6.md
- Build the project (
npm run build), fix any errors, and verify the app runs
- Read and apply
references/upgrade-v6-to-v7.md
- Build the project (
npm run build), fix any errors, and verify the app runs
- Read and apply
references/upgrade-v7-to-v8.md
- Build the project (
npm run build), fix any errors, and verify the app runs
Do not skip intermediate versions.
Step 3: Final Verification
After completing all upgrade steps:
npm run build
If the project uses Capacitor, also run:
npx cap sync
Error Handling
- If
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.
- If Jest or unit tests fail, check the
transformIgnorePatterns configuration — Ionic 6+ ships as ES Modules and requires Babel/Jest configuration updates.
- If CSS styles break after upgrade, check for removed CSS Shadow Parts and renamed CSS variables in the reference file for that version.
- If a multi-version upgrade fails mid-way, fix the current version step before proceeding to the next.
- If the project also uses Capacitor and platform builds fail, the Capacitor version may also need upgrading — use the
capacitor-app-upgrades skill.
Related Skills
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.
1---2name: ionic-app-upgrades3description: Guides 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 capacitor-app-upgrades instead), for plugin library upgrades, or for non-Ionic UI frameworks.4---56# Ionic App Upgrade78Upgrade an Ionic Framework app to a newer major version (4 to 5, 5 to 6, 6 to 7, or 7 to 8).910## Prerequisites1112| Target Version | Angular | React | Vue |13| -------------- | -------- | ----- | ------- |14| 5 | 8.2+ | 16+ | N/A |15| 6 | 12+ | 17+ | 3.0.6+ |16| 7 | 14+ | 17+ | 3.0.6+ |17| 8 | 16+ | 17+ | 3.0.6+ |1819## Procedures2021### Step 1: Detect Current Version2223Read `@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).2425Ask the user for the target version. Default to the latest (8) if not specified.2627### Step 2: Execute Upgrade2829For each major version jump between the current and target version, apply the corresponding upgrade guide **sequentially**:3031| Current to Target | Reference |32| ----------------- | ------------------------------------ |33| 4 to 5 | `references/upgrade-v4-to-v5.md` |34| 5 to 6 | `references/upgrade-v5-to-v6.md` |35| 6 to 7 | `references/upgrade-v6-to-v7.md` |36| 7 to 8 | `references/upgrade-v7-to-v8.md` |3738For multi-version jumps (e.g., 5 to 8), apply each upgrade in order:391. Read and apply `references/upgrade-v5-to-v6.md`402. Build the project (`npm run build`), fix any errors, and verify the app runs413. Read and apply `references/upgrade-v6-to-v7.md`424. Build the project (`npm run build`), fix any errors, and verify the app runs435. Read and apply `references/upgrade-v7-to-v8.md`446. Build the project (`npm run build`), fix any errors, and verify the app runs4546Do **not** skip intermediate versions.4748### Step 3: Final Verification4950After completing all upgrade steps:5152```bash53npm run build54```5556If the project uses Capacitor, also run:5758```bash59npx cap sync60```6162## Error Handling6364* If `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.65* If Jest or unit tests fail, check the `transformIgnorePatterns` configuration — Ionic 6+ ships as ES Modules and requires Babel/Jest configuration updates.66* If CSS styles break after upgrade, check for removed CSS Shadow Parts and renamed CSS variables in the reference file for that version.67* If a multi-version upgrade fails mid-way, fix the current version step before proceeding to the next.68* If the project also uses Capacitor and platform builds fail, the Capacitor version may also need upgrading — use the `capacitor-app-upgrades` skill.6970## Related Skills7172- **`capacitor-app-upgrades`** — If Capacitor also needs upgrading alongside Ionic, use this skill for the Capacitor-specific upgrade steps.73- **`ionic-app-development`** — General Ionic development guidance.74- **`capacitor-plugins`** — For installing or reconfiguring plugins after the app upgrade.
involvex