Not sure that this should be as an experimental feature since it actually give the same behavior without and with vue-router.

Also, I also think that the $route and useRoute() should only changed once the next page is resolved.

I would consider this as a bug fix IMO. Happy to discuss about it if you see it with another POV.

Agreed. However, personally I would advise against using these kind of injections as much as possible in the template as it makes the 'dependencies' of the component less explicit.

Yet the main issue I have is that I'm not sure of the impact on performance. We might be able instead to transform and auto execute useRoute based on usage. What do you think?

@antfu Would love your thoughts on whether it's safe to access _ctx._.provides in this way.

I am not about the approach of injecting on every Vue file. Instead, maybe we should hijack/proxy the vue-router plugin, to register the global $route with our modified one. Or you have already tried that approach?

https://github.com/vuejs/router/blob/98e9af6adbdd4497bbfa6965ec6cd5741c448007/packages/router/src/router.ts#L1215-L1219

Oh, sorry - I updated it in the last commit so it doesn't inject in every file but directly accesses the inject in ctx only if the $route injection is accessed in the template.

@antfu Very up for a different implementation here, but wanted to get this in for 3.7 release.