Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Riot Router

Route logo

Build Status Code Quality NPM version NPM downloads MIT License Coverage Status

Simple isomorphic router

The Riot.js Router is the minimal router implementation with such technologies:

  • compatible with the DOM pushState and history API
  • isomorphic functional API
  • erre.js streams and javascript async generators
  • rawth.js urls parsing

It doesn't need Riot.js to work and can be used as standalone module.

For Riot.js 3 and the older route version please check the v3 branch

Table of Contents


We have 2 editions:

edition file
UMD Version route.js
ESM Module route.esm.js
Standalone UMD Module route.standalone.js

Script injection

<script src=""></script>

Note: change the part x.x.x to the version numbers what you want to use: ex. 4.5.0 or 4.7.0.

ESM module

import { route } from ''


$ npm i -S @riotjs/route

Download by yourself


With Riot.js

You can import the <router> and <route> components in your application and use them as it follows:


    <!-- These links will trigger automatically HTML5 history events -->
      <a href="/home">Home</a>
      <a href="/about">About</a>
      <a href="/team/gianluca">Gianluca</a>

    <!-- Your application routes will be rendered here -->
    <route path="/home">
      Home page
    <route path="/about">
    <route path="/team/:person">
      Hello dear { route.params.person }


    import { Router, Route } from '@riotjs/route'

    export default {
      components { Router, Route }

You can also use the riot.register method to register them globally

import { Route, Router } from '@riotjs/route'
import { register } from 'riot'

// now the Router and Route components are globally available
register('router', Router)
register('route', Route)


The <router> component should wrap your application markup and will detect automatically all the clicks on links that should trigger a route event.

  <!-- this link will trigger a riot router event -->
  <a href="/path/somewhere">Link</a>
<!-- this link will work as normal link without triggering router events -->
<a href="/path/to/a/page">Link</a>

You can also specify the base of your application via component attributes:

<router base="/internal/path">
  <!-- this link is outside the base so it will work as a normal link -->
  <a href="/somewhere">Link<a>

The router component has also an onStarted callback that will be called asynchronously after the first route event will be called

<router onStarted={onRouterStarted}></router>


The <route> component provides the route property to its children (it's simply a URL object) allowing you to detect the url params and queries.

<route path="/:some/:route/:param">

<route path="/search(.*)">
  <!-- Assuming the URL is "/search?q=awesome" -->


Each <route> component has its own lifecycle attributes in order to let you know when it gets mounted or unmounted.

    <route path="/home"


This module was not only designed to be used with Riot.js but also as standalone module. Without importing the Riot.js components in your application you can use the core methods exported to build and customize your own router compatible with any kind of frontend setup.


This module works on node and on any modern browser, it exports the router and router property exposed by rawth

import { route, router, setBase } from '@riotjs/route'

// required to set base first

// create a route stream
const aboutStream = route('/about')

aboutStream.on.value(url => {
  console.log(url) // URL object

aboutStream.on.value(() => {
  console.log('just log that the about route was triggered')

// triggered on each route event
router.on.value(path => {
  // path is always a string in this function

// trigger a route change manually

// end the stream

Base path

Before using the router in your browser you will need to set your application base path. This setting can be configured simply via setBase method:

import { setBase } from '@riotjs/route'

// in case you want to use the HTML5 history navigation

// in case you use the hash navigation

Setting the base path of your application route is mandatory and is the first you probably are going to do before creating your route listeners.

DOM binding

The example above is not really practical in case you are working in a browser environment. In that case you might want to bind your router to the DOM listening all the click events that might trigger a route change event. Window history popstate events should be also connected to the router. With the initDomListeners method you can automatically achieve all the features above:

import { initDomListeners } from '@riotjs/route'

const unsubscribe = initDomListeners()
// the router is connected to the page DOM

// ...tear down and disconnect the router from the DOM

The initDomListeners will intercept any link click on your application. However it can also receive a HTMLElement or a list of HTMLElements as argument to scope the click listener only to a specific DOM region of your application

import { initDomListeners } from '@riotjs/route'