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 🙏

© 2026 – Pkg Stats / Ryan Hefner

router-preact

v0.3.0

Published

Tiny router for Preact apps.

Readme

📡 Router | Preact

Code Coverage by Test Suite License Bundle Size Current Release Version Weekly Downloads Sponsors Known Vulnerabilities

A tiny router for Preact apps. It connects your app with the address bar. That's it.

Features

  • Tiny footprint (less than 1KB gzipped!)
  • No dependencies (BYO Preact/HTM)
  • Comprehensive test suite (100% code coverage)
  • Suitable for production use
  • MIT license
  • Browser-native ESM friendly (designed specifically to require zero build tools to run)

Installing

npm install --save router-preact

Yarn users, you know what to do instead.

Usage

The following examples are written in JSX format, for brevity.

Example: Basic Usage

import { Link, Route } from 'router-preact';

const App = () => <>
  <Route path="/">
    <Link to="/next">Next page</Link>
  </Route>

  <Route path="/next">
    <Link to="/">First page</Link>
  </Route>
</>;

Example: Parameterized Routes

import { Link, Route, pattern } from 'router-preact';

const App = () => <>
  <Route path="/">
    <Link to="/pages/1">Go to page 1</Link>
  </Route>

  <Route path={pattern`/pages/${'pageNumber'}`} render={({ params: { pageNumber } }) => <>
    <p>Thank you for visiting page {pageNumber}.</p>
    <Link to={`/pages/${pageNumber + 1}`}>Go to next page</Link>
  </>}/>
</>;

Example: Redirection

import { Redirect, Route } from 'router-preact';

const App = () => <>
  <Route path="/">
    <Redirect to="/pages/1"/>
  </Route>
</>;

Advanced Example: Intercepting the Router

If you really want to, you can swap out the router implementation by using the Router context provided by this package. For example, if you want to test a component that involves routing.

import { Router } from 'router-preact';

const myRouter = {
  match(path) {
    // If the given path matches the currently active route, then return an object with key-value pairs for each path parameter
    // Otherwise, return `undefined`
  },
  navigate(path) {
    // Transition the currently active route to the given path and notify any callbacks registered via onNavigate() of the new path
  },
  onNavigate: (callback) => () => {
    // Register the callback so that it gets notified when the active route changes
    // Return a function that, when called, will deregister the callback
  },
  path() {
    // Return the path of the currently active route
  },
  query() {
    // Return the query parameters of the currently active route as an object
  }
};

const App = () => <Router.Provider value={myRouter}>
  ...
</>;