feat: vue/vue-router: support vue-router 5

[kleinfreund]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request

Update @ionic/vue-router and @ionic/vue to support vue-router@^5.0.0.

Describe the Use Case

@ionic/vue-router depends on vue-router@^4.0.16.

@ionic/vue depends on @stencil/vue-output-target@0.10.7 which itself has a peer dependency on vue-router@^4.5.0. @stencil/vue-output-target@0.13.1 supports both v4 and v5 (see https://github.com/stenciljs/output-targets/blob/ed5281177542933ebe573e6f3846ff78fa69b652/packages/vue/package.json#L51).

As a consequence, a project depending on either package can't currently upgrade to vue-router@^5.0.0 without overriding transitive dependencies.

Describe Preferred Solution

Ideally, both vue-router v4 and v5 are supported to simplify the upgrade process.

Describe Alternatives

Alternatively, only vue-router v5 is supported. The breaking changes in v5 are minimal and a seamless upgrade should be possible for most dependents.

Related Code

No response

Additional Information

No response

[ShaneK]

Hey! This will be done in v9, which will be the next major release of Ionic Framework.

We will not support both versions at the same time as this isn't really viable for us in the way things are structured on our side, but the migration between v4 and v5 is basically very little in the way we use the router, so the migration effort should be very easy as far as the Vue router goes. You could probbaly even just move to v5 right now on Ionic Framework v8 (we cannot release that as a v8 update though as it would be a breaking change still), just make sure you ignore peer deps. Nothing within Ionic itself should break with the way it's currently used.

There will be other breaking changes in Ionic Framework V9 though when it's released, but those aren't Vue-specific.

[ionitron-bot]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.