Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


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

React Plain Router npm install react-plain-router gzip size

A tiny React router that works exactly as expected with native Javascript:

// App.js
import React from 'react';
import router from 'react-plain-router';

// Wrap it and you can use normal anchor links
export default router(({ path, query, hash }) => (
      <a href="/">Go Home</a>
      <a href="/about">About us</a>

    {path === '/' && <div>Hello world!</div>}
    {path === '/about' && <div>About me</div>}

You have to wrap your app with router() and then both <a> links and window.history.pushState() will work as expected. It will trigger a re-render when any of these properties change: path, query or hash.

If you have parameters or complex routes you can combine it with my other library pagex for a cleaner syntax:

import router from 'react-plain-router';
import page from 'pagex';
export default router(() => (
    {page('/', () => <div>Hello world!</div>)}
    {page('/users', () => <ul>...</ul>)}
    {page('/users/:id', id => <User id={id} />)}

If a link has the attribute target, then this library will ignore it and let the browser handle it. This is very useful for target="_blank", so that the link is opened in a new tab as usual. But it will also work with target="_self", where the router will ignore the link and thus perform a full-refresh.

An event named navigation will be triggered on window every time there's a re-render. You can see the parts with e.detail, which is very useful for debugging:

// When loading /greetings?hello=world#nice
window.addEventListener('navigation', e => {
  console.log('NAVIGATION', e.detail);
  // {
  //   path: '/greetings',
  //   query: { hello: 'world' },
  //   hash: 'nice'
  // }

Internally, it works by using the bubbling events at the document level and then handling any link click. window.location becomes the source of truth instead of keeping an context or global store, which makes it more reliable to interact with native Javascript or http events.


This HOC function accepts a callback, which will be passed an arguments with the props from above and these 3 extra props:

  • path, pathname (String): the current url path, similar to the native pathname. Example: for /greetings it will be '/greetings'. An empty URL would be '/'.
  • query (Object | false): an object with key:values for the query in the url. Example: for /greeting?hello=world it will be { hello: 'world' }.
  • hash (String | false): the hash value without the #. Example: for /hello#there it will be 'there'.

A fully qualified url will parse as this:

// /greetings?hello=world#nice
router(({ path, query, hash, ...props }) => {
  expect(query).toEqual({ hello: 'world' });

Example: navigation bar

We can define our navigation in a different component. <a> are native so they will work cross-components:

// Nav.js
export default () => (
    <a href="/">Home</a>
    <a href="/about">About</a>
    <a href="">Go to Google</a>
    <a href="/terms" target="_blank">Terms and Conditions</a>

Then you can toggle the different pages in the main App.js:

// App.js
import router from 'react-plain-router';
import Nav from './Nav';

export default router(({ path }) => (
    <Nav />
    {path === '/' && <div>Homepage</div>}
    {path === '/about' && <div>About us</div>}

The Google link will open Google, and the Terms and Conditions link will open a new tab. Everything works as expected, in the same way native html works.

Example: scroll to top on any navigation

Add an event listener to the navigation event:

window.addEventListener('navigation', e => {
  window.scrollTo(0, 0);

Example: simulating the <Link>

Just an example of how easy it is to work with react-plain-router, let's see how to simulate the component that the library react-router-dom defines with this library

// components/Link.js
export default ({ to, ...props }) => <a href={to} {...props} />;

Then to use our newly defined component, we can import it and use it:

// Home.js
import router from 'react-plain-router';
import Link from './components/Link';

export default router(() => (
  <Link to="/about">About us</Link>

But you can just use native links:

// Home.js
import router from 'react-plain-router';

export default router(() => (
  <a href="/about">About us</a>

Example: manual navigation

To trigger manual navigation you can use the native history.pushState() as explained in the amazing Mozilla Developer Network:

// src/actions/login
export default id => async dispatch => {
  const payload = await ky(`/api/users/${id}`).json();
  dispatch({ type: 'USER_DATA', payload });
  window.history.pushState({}, 'Dashboard', `/dashboard`);


πŸ›£ A 2kb React router that works exactly as expected with native Javascript








No packages published