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

@zerolith/router

v1.5.0

Published

Typed client-side routing for zerolith: an inference-only route table, plain anchors, loaders, head metadata, and an outlet view

Readme

@zerolith/router

Typed client-side routing for zerolith.

  • defineRoutes({ name: route({...}) }) is an inference-only route table: parameters come from the path string, data from the loader (write load before view), and router.href("release", { tag }) fails to type-check on a misspelled route or a missing parameter.
  • Plain anchors navigate. Same-origin links without modifier keys, download, target, or rel="external" are handled by one delegated click listener; everything else is left to the browser.
  • A route's load runs, and its lazy view resolves, before the URL changes, so the page never shows a half-loaded route; router.pending is true meanwhile.
  • head sets the document title and description per route, statically or from the loaded data.
  • router.ready settles when the initial navigation has committed, router.head is the current route's metadata as a signal, and renderHead from @zerolith/router/server writes it as <title> and <meta> elements, so the same router renders a request on the server and hydrates in the browser. renderRouteState embeds the loaded data in the page, and the browser router reuses it for the initial navigation instead of running the loader twice.
  • base, such as import.meta.env.BASE_URL, serves the application under a path: route paths stay relative to it, href() includes it, and links outside it are left to the browser.
  • Back and forward restore the scroll position; new navigations scroll to the top or to the hash.
  • router.outlet() renders the current route's view, and the fallback for unknown URLs, for the layout to place.

The guide is on the docs site.

Install with npm install @zerolith/router. The API is frozen at 1.0: a breaking change comes only in a major, after a deprecation notice, and the support policy says how long a line gets fixes.

Documentation

  • The routing guide explains it with examples that run as tests.
  • The reference lists every export, generated from the source.
  • New to zerolith? The tutorial builds an app step by step, and the playground runs code in the browser.

License

Apache-2.0. See LICENSE.