router

I cooked some black magic to make it work. resolve posva/unplugin-vue-router#684 Summary by CodeRabbit New Features** Added a navigation guard that validates route parameters before entering pages. Enhanced IDE/type hints for route parameters in page definitions to improve editor autocompletion and correctness checks.

WIP / draft — opening early for visibility, feedback welcome. Closes #2684 Problem When all loaders on a route are lazy, navigation completes while the loaders are still pending. A nested lazy loader (e.g. that s and then keeps loading) leaves the module-level loader current context pointing at its own entry. If a component renders during that window, called in reads that stale context as its parent, which: re-runs the parent loader (the "parent-page" loader is called twice on initial load), makes a loader nest under itself (), and, with two loaders in the same component, spins into an infinite render → reload loop. The context global is set around a loader's execution and restored on ; lazy loaders restore it after navigation, racing with component rendering. Fix In , when invoked from inside a component () and not synchronously within a loader function, drop the ambient context — in a component, loaders are always used at the root. A small depth counter ( / in ) wraps the actual loader-function call so genuinely nested loaders still nest correctly, even when first triggered synchronously from a component. Applied to both and . Test Added a regression test to the shared (runs for basic + Colada): a parent loader that resolves instantly, a child loader that nests it and keeps loading, and parent/child components that use the loaders directly. Written before the fix and confirmed failing first ( warning + parent loader called twice); passes after. Checks [x] — full suite passes (1629) [x] [x] lint + format clean [ ] changelog / docs (if needed)