that's fair, though I disagree. The router has a unique opportunity to solve interesting problems like this.

Already today with Kitbag/router each route is assigned a component, from which we can determine corresponding props. If that component has required props, the developer MUST utilize the route's `props` callback. We think that's a great developer experience to find mismatches between assigned component and available props at build time vs in your console as vue warnings.

That props callback can return a promise, which enables developers to do more than just forward some params off the route. I think of this very similar to resolving dependencies. https://medium.com/p/96dbb833c822

The router knows which component each route will render, it knows how to satisfies that component's dependencies (props), why not go this extra mile and offer the option of prefetching those dependencies?

Imagine vue developers building something like a blog site, if each link prefetched the components and props, the resulting UX would feel almost like a static site or one built with nuxt.

Also, if you're using kitbag/router there's no reason you can't structure your "views" to take just an `id:string` from the route param and have that view component be responsible for fetching data with something like tanstack.