Outils HTML

Gratuit Generateur de snippets Navigation API Router

Generez des snippets de routage JavaScript avec l'API Navigation pour les SPAs, sans History API.

Chargement de l'outil...

Qu'est-ce que Generateur de snippets Navigation API Router ?

The Navigation API is a modern browser API that intercepts navigations through a avigation.addEventListener('navigate', ...) handler. Unlike the History API, which only fires a popstate event on backward/forward traversal, the Navigation API captures all navigation types including link clicks, form submissions, programmatic navigation, and browser back/forward. It integrates with the View Transition API for animated page changes and provides built-in scroll restoration and navigation lifecycle management.

Réponse rapide

Generate client-side routing JavaScript snippets using the Navigation API. Configure route patterns with URLPattern, interception options for link clicks and browser navigation, view transition integration for animated page changes, and scroll restoration behavior. The Navigation API (Chrome 102+, Safari 16.4+, Firefox 131+) replaces the History API with a unified navigate event, AbortSignal for cancellation, and built-in view transition support.

Limites

The Navigation API is not yet supported in all browsers. Chrome 102+, Edge 102+, Safari 16.4+, and Firefox 131+ support it. Older browsers require a fallback to the History API or server-side navigation.
View transition integration requires both the Navigation API and View Transition API support. Cross-document view transitions are a newer feature within the View Transition API and have additional browser requirements beyond the Navigation API baseline.
The Navigation API does not handle application-level concerns like lazy loading, code splitting, or data caching. These must be implemented separately in the route handlers.

Comment utiliser cet outil

Define route patterns using URLPattern objects or simple path matchers. Each route can have a handler function that fetches content and updates the DOM.
Configure navigation interception options: intercept all navigations, only same-origin navigations, or specific navigation types (push, replace, reload, traverse).
Enable view transition integration to animate between page states using document.startViewTransition within the navigate handler.
Select scroll restoration behavior: auto-restore to previous scroll position, scroll to top on each navigation, or custom scroll targets per route.

A quoi il sert

Build a single-page application router with proper back/forward navigation support and no race conditions between concurrent navigation requests.
Create a multi-page application with progressively enhanced client-side navigation that gracefully degrades to full page loads on unsupported browsers.
Implement animated page transitions between views using the View Transition API within the Navigation API navigate handler.

Cas d'usage

Exemples concrets

Exemple

SPA with route patterns and view transitions

A documentation site wants client-side navigation with animated transitions between pages. Use the Navigation API to intercept link clicks, match URLPatterns for each section, call fetch() to load content, wrap the DOM update in document.startViewTransition for crossfade animations, and call navigation.updateCurrentEntry({ state }) to persist search/filter state per route.

Exemple

Multi-page app with progressive enhancement

A content site wants faster navigation without rebuilding as a full SPA. Generate code that intercepts same-origin navigations via navigation.addEventListener('navigate', ...), aborts the current fetch if a new navigation starts (preventing race conditions), updates the main content area, and falls back to full page loads when JavaScript is disabled or the Navigation API is unavailable.

Erreurs frequentes

Not calling event.preventDefault() before calling event.intercept() — the navigate event must be intercepted synchronously to prevent the browser from starting its own navigation. Always call both preventDefault() and intercept() in the handler.
Ignoring the event.signal abort controller — Navigation API provides an AbortSignal on each navigate event. Long-running fetch operations should listen to event.signal to cancel stale requests when a new navigation starts, preventing race conditions.
Forgetting to handle the traversal type navigations — back/forward navigations fire a navigate event with navigationType 'traverse'. Routes need to distinguish between push/replace and traverse to restore scroll position correctly and avoid re-fetching cached content.

Vérification

Open the browser console and navigate between routes using link clicks. Verify that each navigate event fires with the correct navigationType (push, replace, traverse) and that the DOM updates without a full page reload.
Open the Network tab, start a route navigation, and quickly navigate to another route. Verify the first request is cancelled via the AbortSignal by checking for an aborted or cancelled HTTP request in the Network tab.

FAQ

Questions sur Generateur de snippets Navigation API Router

How does the Navigation API differ from the History API for SPA routing?

The History API only fires a popstate event on backward/forward traversal. Link clicks, programmatic pushState/replaceState, and reloads are not captured — you must manually intercept all these paths. The Navigation API fires a single navigate event for every navigation type (push, replace, reload, traverse), plus provides an AbortSignal for cancellation, a FocusChanged event for accessibility, and built-in view transition and scroll restoration support.

Can the Navigation API be polyfilled for older browsers?

There is no full polyfill for the Navigation API because it requires deep browser integration with the navigation engine. For browsers that do not support it (Chrome < 102, Safari < 16.4, Firefox < 131), your SPA should fall back to the History API with manual link click interception, or fall back to full server-side navigation. The generated snippets include a feature detection guard for this purpose.

How do view transitions work with the Navigation API?

Inside the navigate event handler, after calling event.intercept(), wrap your DOM update code in document.startViewTransition(() => { ... }). The browser then captures the old and new page states, creates a crossfade animation between them, and updates the DOM inside the transition callback. The Navigation API's viewTransition option on intercept() can optionally handle this integration automatically in supported browsers.

Outils lies