route-migration

Vue2 route migration to Vue3 filesystem-based routing uses a central mapping table to convert pages.json configurations into automated route definitions. It replaces manual route declarations by enforcing PageRoute types and integrating TypedRouter across multi-page uni-app projects.

A route migration mapping table, defined in route-migration-map.yml, establishes the source-to-target relationship between Vue2 pages.json entries and Vue3 filesystem-based routes. It serves as the single source of truth to drive automated route generation and type-safe navigation integration.

Compile-time safety for typed routing in uni-app projects is ensured by defining PageRoute and PageParams types alongside a TypedRouter helper. This setup validates isValidRoute logic and wires up a cohesive router helper set for type-safe navigation.

Yes, this Vue2 route migration workflow supports multi-page uni-app projects by providing automatic route generation and validation. It integrates TypedRouter across the project to ensure type-safe navigation and full end-to-end migration coverage.

The best way to convert pages.json routing configurations to definePage usage is by applying a central mapping table that enforces the route-migration map. This approach integrates TypedRouter to ensure compile-time safety and automatic route generation across the project.