focus-router

🚨 HEYO! - This code is no hack job; this is a well-thought-out router with immense focus and a fluent API that is a breeze to work with: It has to be amazing if it will become the de-facto standard for all React websites and the next generation of mobile web apps.

npm install focus-router

This is the most golfed router ever made, and it's no slouch! Focus Router is used across all my companies (one with multi-million dollar revenue, another with over >1M in seed funding). Focus Router's goal is to be opinionated, thorough, and handy enough to be the #1 React Router.

Example

React app with a Home Page route, demonstrating the savage focus of Focus Router.

import React from 'react';
import { createRoot } from 'react-dom/client';
import { Stack, defineRoute } from 'focus-router';

defineRoute('HomePage', '/', () => (
  <div>Home Page</div>
));

createRoot(document.getElementById('root')).render(<Stack/>);

Aside from simplicity, Focus Router has a fuller feature set than React Router (55 KB) which suffers from a lack of focus, which is why this router exists!

1. No need to use <Link/>. Just use plain <a>tags
2. Swap useState() for screen.useParam() or screen.useQueryParam() to use a browser history-backed global state
3. Can disable navigation with useUnsavedChanges()
4. Minimal re-renders and maximum micro-optimization

A complete example

This is a much more likely use case. In it we are using multiple stacks because we have several different route types, as well as modals that must appear on top of everything in the dom.

import React, { Fragment } from 'react';
import { createRoot } from 'react-dom/client';
import { Stack, defineRoute, usePath } from 'focus-router';

defineRoute('HomePage', '/', HomePage);
defineRoute('AdminPage', '/admin', AdminPage, 'admin');
defineRoute('AppPage', '/app', AppPage, 'app');
defineRoute('Settings', '/settings', SettingsModal, 'modal');


const App = () => {
  const path = usePath();
  const {loggedIn, loggingIn} = useUserStatus(); // some custom hook

  const renderBody = () => {
    if (loggingIn) return <SplashScreen/>;
    if (path.startsWith('/app')) {
      if (!loggedIn) return <Login/>;
      return <Stack filter="app"/>;
    }
    if (path.startsWith('/admin')) {
      if (!loggedIn) return <Login/>;
      return <Stack filter="admin" mode="screen"/>;
    }
    return <Stack/>;
  };

  return (
    <Fragment>
      {renderBody()}
      <Stack filter="modal"/>
    </Fragment>
  );
};

Wow! A lot going on... Let's break it down. This is not a contrived example, it's a real world example, so I'll explain what's going on.

There are several Stack components in use here, and that is to control where each stack is placed in the dom. You don't want modals appearing in the same z-index as the screens.

Since my admin routes start with "/admin" I do a check to see if the path starts with "/admin" and if so, I render a stack with a filter of "admin". This means that only routes with a type of "admin" will be rendered in this stack. I also set the mode to "screen" which means that only one screen will be rendered at a time.

The webapp (in contrast with the HomePage) is located at '/app', so I do a similar check for that. I also check if the user is logged in, and if not, I render a login screen. If the user is logged in, I render a stack with a filter of " app" and a mode of "stack". This means that multiple screens will be rendered at a time, and only screens with a type of "app" will be rendered.

If the user is not on a specially handled route, I render a stack with no filter. This stack will contain all the routes that have no type specified.

Finally, I render a stack with a filter of "modal". This means that only routes with a type of "modal" will be rendered in this stack.

Since there is no CSS yet, you'll quickly realize the stack contents are ahem stacking vertically by default, which is obviously where your CSS skills come in.

Documentation

Let's jump in to documentation by going over the most important function first.

Route Definition

import { defineRoute } from 'focus-router';

Some React routers have routes defined in <Route/> tags, but in Focus Router, routes are defined at the root level of the code. You can put a bunch of these next to each other to define all the routes. You can put these at the root level, even in the same file as createRoot. Focus Router will prioritize higher routes first when matching.

defineRoute(name, path, component, type);

Name	Type	Description
name	String (Required)	A unique name for the route. Can be passed as the first argument to navigation.go()
path	String (Required)	A pattern such as /blog. Navigating to a URL that looks like this pattern will cause the route to become active.
component	Component (Required)	A component to render.
type	String (Optional)	A string you want to group fragments of stacks by, you can pass this as filter to a <Stack/> to make the stack filter by this type.

You can re-use concepts from other routers based on path-to-regexp (eg: React Router, React Navigation and FlowRouter). Although path-to-regexp is not used, the following paths are all still valid when brought forth to Focus Router:

• "/blog/:postId"
• "/search/:term?"
• "*"

React Component: <Stack/>

import { Stack } from 'focus-router';

const App = () => (
    <Stack filter="demo" mode="stack"/>
);

By default, this will simply render a div with contents of the routes in the browser history stack with no types specified. You can specify a filter to only render certain routes. You might think about this like an "Outlet" from other routers.

Stacks have two presentation modes:

• screen is your basic bog standard router, it will render only one screen at a time. This is what you typically think of in a router.
• stack (default) on the other hand is more like a mobile app, where you can navigate to a new screen, and the old screen will stay in the background. This is useful for building full blown apps with animations.

Navigation

import { navigation } from 'focus-router';

You can use navigation to navigate programmatically. There are multiple functions to facilitate navigation as follows:

go

navigation.go(target, params, queryParams, opts)

Argument	Type	Description
target	Boolean (Optional)	A path or a route name to navigate to. If target starts with a slash, it will immediately be navigated to and params and queryParams are ignored. If target is a routeName, a path will be created using all the arguments.
opts	Object (Optional)	Navigation options, which are replaceState (defaults to false) and scrollToTop (defaults to true).

• {replaceState: true} will replace the state, instead of adding to the state history.
• {scrollToTop: false} will maintain the scroll position across navigations.

setParams

navigation.setParams(params, opts)

Short hand for navigation.go, only changes the params (Object).

setQueryParams

navigation.setQueryParams(params, opts)

Short hand for navigation.go, only changes the query params (Object).

Screen Props

Each screen in the stack will receive the screen, isVisible, and animateIn props.

const UserProfile = ({screen, isVisible, animateIn}) => {
  // Can use query params here with screen.useQueryParams()!
  return <div/>;
};

• screen.useParam(key, defaultValue) Returns a param from the URL using the route definition
• screen.useQueryParam(key, defaultValue) Returns a query param from the URL
• screen.useRouteName() Returns the name (String) of the currently presented route.
• screen.usePath() Returns the path (String) of the currently presented route.

Create Link

import { createLink } from 'focus-router';

Returns a URL that can be navigated to. This can be useful to create a dynamic <a> tag, or to dynamically go to different routes. params and queryParams are encoded within the string.

Argument	Type	Description
routeName	String (Required)	Must match a route name from a defineRoute().
params	Object (Optional)	Params to encode into the path corresponding to the routeName
queryParams	Object (Optional)	Params to encode into the query string

Prevent Navigation

import { useUnsavedChanges } from 'focus-router';

Using this will cause navigating away from the current URL (such as clicking a link or using the back button) to be ignored. When the stack is empty, the browser's native Save Changes modal will be presented.

Argument	Type	Description
active	Boolean (Optional)	Turns the effect on or off

Bonus Utils

These handy utils are there if you need them, only because focus router needs them internally.

import { 
  createBus, 
  useBus,
  encodeQueryString, 
  encodeSearchString, 
  parsePathParams,
  randomId,
} from 'focus-router/util';