This happens even when the wildcard route is a child route of '/', which is kinda strange. I do think that "root" routes should have higher priority than child routes.

Hey, thanks for opening the issue.
This is indeed a caveat of dynamically added routes. FTM you'll have to add the wild card route after any other route.

ping @fnlctrl @yyx990803

Maybe there could be an option to prepend the new routes instead of appending them?

Hmm maybe dynamically added routes should have higher priority than the statically defined ones?

@Dadibom Yeah an option seems nice

Another option would be to optionally make addRoutes override old routes (.addRoutes(newRoutes,{ override: true })), so you can construct a new routes array externally the way you need it?

We can also keep track of any asterisk route (path: '*') so dynamically added routes are always added before that one.
People will still have issues if there's some route with foo-* and they dynamically add routes like foo-lol and foo-bar but I don't see a real world example about a partial asterisk while having an asterisk route is very common

I'd be fine with any of the solutions mentioned, but I think the most transparent one would be appendRoutes / prependRoutes / replaceRoutes

Is there an update for this? I just ran into it. I think that keeping track of path: '*' and adding dynamic routes before it as suggested by @posva is the simplest, quickest solution. However as a more complete fix that would give more flexibilities, I think being able to appendRoute/prependRoute makes more sense.

well... i've got two main views (routes) that each have their own layouts. the * route is a child route to my main view. when i add the second view (admin), i still cannot access it. prepend/replace would be great.

@LinusBorg Your answer solved my doubts. But I didn't find any information about { override: true } in the document

Because it is a suggestion, not an existing feature.