chore(vue-router): upgrade vue-router to 5.2.0, vite to ^8

[ShaneK]

Issue number: internal

---

What is the current behavior?

@ionic/vue-router, @ionic/vue, and the vue3 test app pin vue-router at 5.0.6. The test app's dev and test toolchain is also several majors behind: vite 3, vitest 1, @vue/test-utils 2.0.0-rc.18, and jsdom 20.

vue-router 5.1+ declares an optional peer on vite ^7 || ^8 (for its experimental typed-routes unplugin), which the vite 3 pin can't satisfy. So bumping vue-router on its own forces --legacy-peer-deps on every test app install.

What is the new behavior?

This bumps vue-router to 5.2.0 across @ionic/vue-router, @ionic/vue, and the vue3 test app. The wrapper needed no source changes: every vue-router API it imports (createRouter, createWebHistory, parseQuery, RouteLocationNormalized, and so on) is unchanged between 5.0.6 and 5.2.0. The 5.1 and 5.2 changes target the experimental typed-routes unplugin, scrollBehavior, and some other stuff Ionic doesn't use.

It also modernizes the test app toolchain to vite 8, vitest 4, @vitejs/plugin-vue 6, @vue/test-utils 2.4.11, and jsdom 30, and raises the app's Node engine floor to match. With vite on 8, vue-router's optional vite peer now resolves on its own, so the install no longer needs --legacy-peer-deps.

Also fixing a flaky playwright test

Does this introduce a breaking change?

• Yes
• No

Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ionic-framework	Ready	Preview, Comment	Jul 27, 2026 7:26pm