router-dom

A lightweight router for single-page applications with faster subsequent page-loads by prefetching links during idle time if the user is not saving data.

• it helps to reduce the delay between your pages, to minimize browser HTTP requests and enhance your user's web experience.
• library agnostic.
• simple: define your routes, start to listen global event and to route changes.
• base href support.
• opt-in errorHandler and formHandler.
• support in all modern browsers.
• Dynamic route params and nested Routes.

Simple: https://codepen.io/FabianK/pen/vYxXjwv?editors=1000
Advanced: https://page-transitions-router.netlify.app

With npm:

$ npm i router-dom

or via CDN:

<script type="module">
  import Router from "https://cdn.skypack.dev/router-dom";
  new Router(...) // see Constructor Documentation
</script>

<a href="/">Home</a>
<a href="/about">About</a>

<div data-outlet></div>

path-to-regexp: Turn a path string such as '/user/:name' into a regular expression
hydro-js: Renders the view. In order to pass state via an anchor element (data attribute), a mapping on the hydro object is needed.

• window: beforeRouting & afterRouting

The router class takes an array with at least one entry. Only the path is mandatory.
Either a template or and element will be rendered in your element with attribute data-outlet.
You can also specifiy one-level of children.
One more interesting property is the restoreScroll. Scroll positions are stored per history entry, like the browser does natively: every entry gets an internal __routerScroll key inside history.state, and its position is persisted in sessionStorage under router-scroll. New navigations always start on top, history traversal (back/forward) restores the position of that entry, and reloads are restored by the browser itself (history.scrollRestoration is handed back to auto on pagehide), so SSR pages do not flash. BFCache restores stay untouched. Restoration keeps correcting while late-rendered content grows and aborts as soon as the user scrolls. No consumer setup is required; scrollBehavior only applies to the top reset of new navigations. The second argument is the optional object options: it can take a general errorHandler, a formHandler, a fetchOptions for the form and the scrollBehavior. Set viewTransitions: true to wrap client-side route DOM commits in document.startViewTransition() when available. If there is a formHandler, form submits will handled via attributes on the form element and fetch.

const router = new Router([
  {
    path: "/",
    restoreScroll: true, // defaults to true
  },
  {
    path: "/about",
    templateUrl: "/about.html",
    leave: ({ from, to, params, state }) => {},
  },
  {
    path: "/contact/:name",
    element: "<h2>Drop a message on [...]</h2>" // or an actual Node Element,
    beforeEnter: ({ from, to, params, state }) => {},
    afterEnter: ({ from, to, params, state }) => {},
  },
]);

Set data-router-path on the route outlet to current pathname, optionally including query string, when server already rendered that route:

<main data-outlet data-router-path="/about">Server-rendered content</main>

When the marker matches a configured route, the constructor adopts the existing DOM, skips the duplicate initial template request and render, then consumes the marker. Later navigation behaves normally. Missing or stale markers keep the original client-rendered startup behavior.

Use router.destroy() when the router's document ownership ends, such as an HMR replacement or an island teardown. It cancels pending router work and releases its popstate and DOM observers. Links marked with data-router-back use history traversal, allowing the router to restore the saved scroll position for the previous entry:

<a href="/directory" data-router-back>Back</a>

• Takes a path, a state object and optional params. Will redirect to the path.

• Removes a route from the route registry.

• Adds a route object to the route registry.

• Replaces a route with a new one in the route registry.

router.routes returns a frozen snapshot for inspection. Use addRoute, removeRoute, and modifyRoute for mutations. Only one Router instance should own browser navigation per document.

• Replaces the router options.

• Returns the params as key-value pair.