![Solved] Vue3 Configuration routing error: Catch all routes (“*“) must now be defined using a param with a custom regexp. | ProgrammerAH Solved] Vue3 Configuration routing error: Catch all routes (“*“) must now be defined using a param with a custom regexp. | ProgrammerAH](https://programmerah.com/wp-content/uploads/2021/07/20210706183921321.png)
Solved] Vue3 Configuration routing error: Catch all routes (“*“) must now be defined using a param with a custom regexp. | ProgrammerAH
![Complete Vue Router 4 Guide: Basics, Programmatic Routing, Navigation Guards, Transition Effects and Composition API | by OnlyKiosk Dev Tech | Level Up Coding Complete Vue Router 4 Guide: Basics, Programmatic Routing, Navigation Guards, Transition Effects and Composition API | by OnlyKiosk Dev Tech | Level Up Coding](https://miro.medium.com/max/1400/1*Jpk1mORsAIf_X2a2v3WZ4A.png)
Complete Vue Router 4 Guide: Basics, Programmatic Routing, Navigation Guards, Transition Effects and Composition API | by OnlyKiosk Dev Tech | Level Up Coding
![this.$route.params is empty in app.vue when building site global navigation (outside of router-view) - Stack Overflow this.$route.params is empty in app.vue when building site global navigation (outside of router-view) - Stack Overflow](https://i.stack.imgur.com/ZvAcy.png)
this.$route.params is empty in app.vue when building site global navigation (outside of router-view) - Stack Overflow
![Typescript: `Location` interface typing for params should be more permissive · Issue #2662 · vuejs/vue-router · GitHub Typescript: `Location` interface typing for params should be more permissive · Issue #2662 · vuejs/vue-router · GitHub](https://user-images.githubusercontent.com/2202989/54756088-c5d35200-4be7-11e9-8e07-ea27793a84ee.png)