Why routekit

If you’ve reached for react-router, vue-router, or @tanstack/router and felt like you were getting a cathedral when you wanted a hut, routekit is for you. It does one thing — match URLs to handlers in a type-safe way — and gets out of your way.

Getting Started Install in under a minute.

API Reference Every export, every option.

Examples Working SPAs you can copy.

Changelog What changed and when.

Five-line example

import { createRouter } from 'routekit';

const router = createRouter([
  { path: '/',           handler: () => import('./pages/home') },
  { path: '/posts/:id',  handler: () => import('./pages/post') },
]);

router.start();

That’s the whole API surface for 80% of apps. No providers to mount, no context to thread, no compile-time codegen step.

What routekit is not

It is not a framework. It is not a data-loading library. It is not a server. It does not ship with a CSS reset, a state manager, or an opinion about your folder structure. It is ~3 KB of TypeScript that turns window.location into typed events.

If your app needs more than that — server rendering, file-system routing, layout nesting — reach for a framework. routekit shines when the rest of the app is already opinionated and the routing layer needs to stay quiet.