npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@symfa/react-router-helpers

v1.0.3

Published

The goals for that library are simplify, standardize and shift responsibility for the route protection from component to library.

Downloads

11

Readme

Why do you need it?

The goals for that library are simplify, standardize and shift responsibility for the route protection from component to library.

What the library can do:

  • Route protection (guard)
  • Providing data for component pages (resolver)
  • Lazy component support out of the box
  • If the user doesn't have access to the lazy component, then the lazy component won't even be loaded over network
  • Show loading component and provide detailed statuses with hooks on each step of component loading

Well, of course, the library includes a simple, react-style and not overloaded interface for interacting with the library. 😃

Requirements:

  • React v16.8.0+
  • React Router DOM v6.0.0+

Setup:

  • npm i react-router-dom@6

  • npm i @symfa/react-router-helpers

Configuration:

NOTE: Follow the default tutorial for basic configuration!

How to migrate from react-router-dom:

Since the 6 version of react-router - the more convenient way of using the router is with javascript objects, this way allows to have more smooth experience.

To fully migrate you need to:

  • Just need to replace useRoutes with useRoutesWithHelper
  • Replace <Outlet /> to <HelperOutlet /> in all places
  • If you are using Route and component style - you need to wrap your component into <RouteHelper />

Example - before migration default react-router-dom:

import { useRoutes } from 'react-router-dom';

function App() {
  let element = useRoutes([
    {
      path: '/',
      element: <Dashboard />,
      children: [
        {
          path: 'messages',
          element: <DashboardMessages />,
        },
        { path: 'tasks', element: <DashboardTasks /> },
      ],
    },
    { path: 'team', element: <AboutPage /> },
  ]);
  return element;
}

Example - after migration with replaced useRoute to useRoutesWithHelper:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      element: <Dashboard />,
      children: [
        {
          path: 'messages',
          element: <DashboardMessages />,
        },
        { path: 'tasks', element: <DashboardTasks /> },
      ],
    },
    { path: 'team', element: <AboutPage /> },
  ]);
  return element;
}

Example - before migration <Outlet />:

import { Outlet } from 'react-router-dom';

function Dashboard() {
  return (
    <div>
      <h1>Dashboard</h1>
      
      <Outlet />
    </div>
  );
}

Example - after migration to <HelperOutlet />:

import { HelperOutlet } from '@symfa/react-router-helpers';

function Dashboard() {
  return (
    <div>
      <h1>Dashboard</h1>

      <HelperOutlet />
    </div>
  );
}

Example before migration - component style Route:

root.render(
  <BrowserRouter>
    <Routes>
      <Route path='/' element={<Dashboard />} />
    </Routes>
  </BrowserRouter>
);

Example after migration - component style Route:

import { RouteHelper } from '@symfa/react-router-helpers';

root.render(
  <BrowserRouter>
    <Routes>
      <Route path='/' element={<RouteHelper element={<Dashboard />} />} />
    </Routes>
  </BrowserRouter>
);

Example after migration - component style Route how to pass props:

import { RouteHelper } from '@symfa/react-router-helpers';

root.render(
  <BrowserRouter>
    <Routes>
      <Route path='/' element={<RouteHelper
        element={<Dashboard />}
        guards={[authorizationGuard]}
      />} />
    </Routes>
  </BrowserRouter>
);

That's all, the library's functionality can be fully used!

There are 3 types of entities in the library:

  • Guard
  • Resolver
  • Lazy component

All of them have indicators of work - statuses, there are 4 types of statuses in total:

  • Initial - Not initiated yet
  • Loading
  • Loaded
  • Failed - Couldn't work for some reason

You can get statuses inside the LoadingComponent component:

  • To get guard statuses - useGuardStatus
  • To get resolver statuses - useResolverStatus
  • To get lazy component statuses - useLazyStatus

Statuses are needed for more flexible display of indicators loads and errors. LoadingComponent, in addition to accepting statuses, is also used as a loading indicator - a loader.

Check out more our examples!

Guard:

When you need to 'guard' a page from an unauthorized user or a regular user from the admin page - guards will be helpful to you. You just need to create the guard itself and use it on the needed route. Here is what the created guard looks like that will not let an unauthorized user to hit the page of your application:

Example:

export const authorizationGuard = () => () => {
  return localStorage.getItem('token') !== null;
};

Usage:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      element: <Dashboard />,
      guards: [authorizationGuard],
    },
  ]);
  return element;
}

In other words, the guard must return true if the user can enter the given route and false if user cannot enter. Protection for our route - ready!

To handle the situation when the guard returned false and the page was not loaded, we need to add a loadingComponent and inside that component we have access to hooks that can tell us about status changes of the guard!

Example creating a loading component with a redirect:

import { useGuardStatus, RouteHelperStatus } from '@symfa/react-router-helpers';

export const LoadingComponent = () => {
  const guardStatus = useGuardStatus();
  const navigate = useNavigate();

  useEffect(() => {
    if (guardStatus === RouteHelperStatus.Failed) {
      navigate('/login');
    }
  }, [guardStatus]);
  
  return <>Loading...</>;
};

Example usage:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      element: <Dashboard />,
      guards: [authorizationGuard],
      loadingComponent: <Loading />
    },
  ]);
  return element;
}

More detailed information about guards:

  • Guards can be either synchronous or asynchronous.
  • In the guard, you can use hooks to get data from the store/route params or dispatch actions.
  • If the guard returns false - then the status of the guard is Failed
  • Guard statuses can be received inside LoadingComponent using the useGuardStatus hook
  • Since the guards field in the route is an array, there can be several guards
  • The order in which guards are called is the same as they placed in an array - from left to right
  • As soon as one guard returns false, all guards on the right of failed one are not called.
  • If the guard threw an error, and it was not wrapped in a try catch block within the guard, then the guard's status will be Failed.

Example guard with dispatch:

export const userProfilePageGuard = () => {
  const params = useParams();
  const user = useSelector();
  
  return () => {
    return params.id === user.id;
  };
};

Example guard with status receiving:

import { useGuardStatus } from '@symfa/react-router-helpers';

export const LoadingComponent = () => {
  const guardStatus = useGuardStatus();

  useEffect(() => {
    console.log(guardStatus);
  }, [guardStatus]);
  
  return <>Loading...</>;
};

Resolver:

It happens that you need to show a component and first pull data from the server to it, and usually you have to use useEffect, load data, use useState to indicate data loading, and this is where resolver comes to our help.

Example - resolver creation:

export const userInfoResolver = () => async () => {
  const userInfo = await getUserInfo();
  
  return userInfo;
};

Example resolver usage:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      element: <Dashboard />,
      resolvers: {
        userInfo: userInfoResolver
      },
    },
  ]);
  return element;
}

While the data is being loaded, you can show a loading indicator using LoadingComponent

Example resolver with loading indicator - LoadingComponent:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';

const Loading = () => {
  return <>Loading...</>;
};

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      element: <Dashboard />,
      loadingComponent: <Loading />,
      resolvers: {
        userInfo: userInfoResolver
      },
    },
  ]);
  return element;
}

As soon as the resolvers finish their work, the component will be rendered and the data that the resolvers will return can be received with the hook - useResolver

Example receiving data with hook useResolver:

import { useRoutesWithHelper, useResolver } from '@symfa/react-router-helpers';

export function Dashboard() {
  const { userInfo } = useResolver();
  
  return (<>
    <h2>Dashboard Page</h2>
    <h2>{userInfo.name}</h2>
  </>);
}

More detailed information about resolvers:

  • Resolvers can be either synchronous or asynchronous.
  • Resolvers, unlike guards, run simultaneously
  • In the resolver, you can use hooks to get data from the store / route parameters or dispatch actions.
  • Resolver statuses can be received inside LoadingComponent with the useResolverStatus hook
  • Since the resolvers field in the route is an object, there can be multiple resolvers.
  • The name of the key in the resolvers object is the name of the key to get values inside the component when using the useResolver hook.
  • If the resolver threw an error, and it was not wrapped in a try catch within the resolver, then the resolver status will be Failed.

Example usage with redux toolkit:

export const profilePageResolver = () => {
  const params = useParams();
  const dispatch = useDispatch();

  return async () => {
    await dispatch(fetchUserById(params.userId));
  };
};

Example with status receiving inside LoadingComponent:

import { useResolverStatus } from '@symfa/react-router-helpers';

export const LoadingComponent = () => {
  const resolverStatus = useResolverStatus();

  useEffect(() => {
    console.log(resolverStatus);
  }, [resolverStatus]);

  return <>Loading...</>;
};

Lazy Component:

The library supports lazy components out of the box and allows you to use them without additional wrapper - React.Suspense and also allows using guards to stop lazy component from loading - if the user does not have access to the page / component - by the Angular analogy canLoad.

Example - default usage of lazy component with react-router-dom:

import { useRoutes } from 'react-router-dom';
const Dashboard = React.lazy(() => import('./pages/Dashboard'));

function App() {
  let element = useRoutes([
    {
      path: '/',
      element: (
        <React.Suspense fallback={<>Loading</>}>
          <Dashboard />
        </React.Suspense>
      ),
    },
  ]);
  return element;
}

Example - usage with library:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';
const Dashboard = React.lazy(() => import('./pages/Dashboard'));

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      lazyElement: <Dashboard />,
    },
  ]);
  return element;
}

If you need to show loading indicator - you can use LoadingComponent

Example - using lazy component and show loading:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';
const Dashboard = React.lazy(() => import('./pages/Dashboard'));

const LoadingComponent = () => <>Loading...</>;

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      lazyElement: <Dashboard />,
      loadingElement: <LoadingComponent />
    },
  ]);
  return element;
}

More detailed information about lazy component:

  • If the lazy component has a guard on the router that returns false, the lazy component will not even start loading over the network. In other words, a user who should not have access to the requested page / component will not download its bundle.
  • With a lazy component, you can also use resolvers and get values with useResolver inside the lazy component
  • Detailed information about statuses lazy component can be received inside LoadingComponent with the useLazyStatus hook
  • If some error occurred while loading the lazy component (for example, the Internet connection was interrupted) - then the status of the lazy component will be Failed
  • If some error occurred while loading the lazy component (for example, the Internet connection was interrupted) - then detailed information about the error can be received inside the lazy loading component with the hook - useLazyError

Example with receiving lazy component statuses:

import { useLazyStatus } from '@symfa/react-router-helpers';

export const LoadingComponent = () => {
  const lazyStatus = useLazyStatus();

  useEffect(() => {
    console.log(lazyStatus);
  }, [lazyStatus]);

  return <>Loading...</>;
};

Example - with receiving lazy component error:

import { useLazyStatus, useLazyError } from '@symfa/react-router-helpers';

export const LoadingComponent = () => {
  const lazyStatus = useLazyStatus();
  const lazyError = useLazyError();

  useEffect(() => {
    console.log(lazyStatus);
  }, [lazyStatus]);

  useEffect(() => {
    console.log(useLazyError);
  }, [useLazyError]);

  return <>Loading...</>;
};

Loading Component:

Loading component - a usual component and a generic way to show loading and handle status changes from guards, resolvers and from lazy component. Inside the Loading component, you can use the standard react hooks / dispatch actions. To simply show the loading while guards, resolvers, lazy components are loading / working, you just need to create simple Loading component:

Example - with loading:

export const LoadingComponent = () => {
  return <>Loading...</>;
};

Example - usage of LoadingComponent:

import { useRoutesWithHelper } from '@symfa/react-router-helpers';

function App() {
  let element = useRoutesWithHelper([
    {
      path: '/',
      element: <Dashboard />,
      loadingElement: <LoadingComponent />
    },
  ]);
  return element;
}

If you need to handle statuses from guards, resolvers, lazy components - then you can use hooks

  • For guards - useGuardStatus
  • For resolvers - useResolverStatus
  • For lazy component - useLazyStatus
  • To get detailed information about lazy component error - useLazyError

Example - of usage LoadingComponent:

import { useGuardStatus, useResolverStatus, useLazyStatus, useLazyError, useNavigate } from '@symfa/react-router-helpers';
import { RouteHelperStatus } from './types';

const LoadingComponent = () => {
  const guardStatus = useGuardStatus();
  const resolverStatus = useResolverStatus();
  const lazyComponentStatus = useLazyStatus();
  const lazyError = useLazyError();
  const navigate = useNavigate();

  useEffect(() => {
    if (lazyError?.error) {
      navigate('/error-page');
    }
  }, [error]);

  useEffect(() => {
    if (guardStatus === RouteHelperStatus.Failed) {
      navigate('/login');
    }
  }, [guardStatus]);

  useEffect(() => {
    if (resolverStatus === RouteHelperStatus.Failed) {
      navigate('/error-page');
    }
  }, [resolverStatus]);

  useEffect(() => {
    console.log(lazyComponentStatus);
  }, [lazyComponentStatus]);

  return <>Loading</>;
};