Client side routing for React applications. Inspired by Next.js.
It supports history management, dynamic routing, and link creation.
This npm package provides TypeScript files, and it is your responsibility to build and bundle it.
But Why?
This library is designed to be as simple as possible. It does not include any dependencies, making it easy to understand and modify. Additionally, this approach results in a smaller bundle size.
I need a bundled version.
You can still fork the library and modify the package.json
. For configuration details, see rollup.config.js.
To build the package, run:
npm run build
Update your package.json
like this:
{
"main": "dist/cjs/index.js",
"module": "dist/esm/index.js"
}
const { navigate, route } = useRouter();
navigate({ pathname: "/new-route" });
console.log(route);
// {
// path: "/new-route",
// pathname: "/new-route",
// params: {},
// }
const { navigate, route } = useRouter();
navigate(
{ pathname: `/dynamic-route/${12}`, query: { key: "value" } },
{ replace: true },
);
console.log(route);
// {
// path: "/dynamic-route/12",
// pathname: "/dynamic-route/:id",
// params: { ":id": "12", key: "value" },
// }
npm install router2
The BrowserRouter component is the main component of this library. It uses React Context to provide routing functionality to its children.
<BrowserRouter routes={routes} />
routes
: This is a record object mapping route paths to React components. The "/404" path should be mapped to a component that will be displayed when no other route matches.
const routes = {
"/": () => <HomePage />,
"/about": () => <AboutPage />,
"/404": () => <NotFoundPage />,
};
<BrowserRouter routes={routes} />;
const routes = {
"/": () => <HomePage />,
"/about": () => <AboutPage />,
"/404": () => <NotFoundPage />,
};
<BrowserRouter routes={routes}>
{(Page) => (
<InRouterContextProvider>
<Page />
</InRouterContextProvider>
)}
</BrowserRouter>;
The Link component creates an anchor element that interacts with the router.
<Link pathname="/some-route" query={{ key: "value" }} replace />
Properties
pathname
: The path of the route to navigate to when the link is clicked.query
: An optional object representing the search parameters of the URL.replace
: An optional boolean indicating whether the current history entry should be replaced instead of creating a new entry.- All other properties of the anchor element are also supported.
The useRouter
hook returns the router object.
const router = useRouter();
Returns Router
object.
This type represents a router object. It has the following properties:
path
: The path of the current route.navigate
: A function to navigate to a different route. It takes aHistory
object and an optional options object as parameters.pathname
: The path of the current location.params
: An object representing the URL parameters and search parameters.
This type represents a history entry. It has the following properties:
path
: The path of the current route.pathname
: The pathname of the location.query
: An optional record object representing the search parameters of the URL.
Feel free to contribute to this project by submitting issues and pull requests.
This project is licensed under the MIT License - see the LICENSE file for details.