12-route-guards

Session-aware route guards wait for session bootstrap before evaluating access, preventing flicker. This ensures the auth store is fully hydrated so route guards apply authentication, guest, and role-based access controls without premature redirects.

Configure role-based access control by applying require-role guards using route metadata. The guards check the central auth store to secure privileged areas, enforcing role-based routing permissions after the session state is successfully bootstrapped.

Apply guest guards to login and register routes to prevent authenticated users from accessing them. The guard checks the central auth store and redirects logged-in users away from guest-only screens once the session is active.

Redirect handling preserves the user's intended destination URL during route guard redirects. When an auth guard blocks a private route, it saves the return URL so the application can navigate the user back to their original destination after authenticating.

Yes, optional deactivation guards can be applied to prevent navigation away from pages with unsaved changes. These route guards intercept routing events to secure privileged areas and protect against accidental data loss during session-aware navigation.

Frontend routing allows unauthorized access when route guards evaluate before the session is hydrated. Implementing session-aware guards that wait for session bootstrap ensures the central auth store is fully loaded before enforcing authentication and role-based access controls.