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

@helloharusystem/s-spa

v0.2.0

Published

Tiny template-based SPA router: HTML <template> rendering + pushState routing, no framework.

Readme

s-spa

A tiny, framework-free SPA router built on native <template> elements and pushState. No virtual DOM, no bundler required to use it.

Install

npm install @helloharusystem/s-spa

Development

To work on the library itself:

npm install
npm run build

Usage

<div id="view-container"></div>

<template id="home"><h1>Home</h1></template>
<template id="settings"><h1>Settings</h1></template>
<template id="login"><h1>Login</h1></template>
import { createRouter } from "@helloharusystem/s-spa";

function requireAuth(templateId) {
  if (!isLoggedIn()) return "login";
}

const router = createRouter({
  container: "#view-container",
  guard: requireAuth, // runs before every navigation
});

router.route("home", "/");
router.route("settings", "/settings", { guard: requireAuth }); // stacks on top of the global guard
router.route("login", "/login");

router.registerPageHandler("settings", () => {
  // wire up this page's DOM after it renders
});

router.start(); // renders whatever the current URL resolves to

Guards: global vs. per-route

createRouter's guard option runs before every navigation — good for cross-cutting checks most of your pages share, like "must be logged in." router.route(id, path, { guard }) runs only for that route, after the global guard passes — good for the minority of pages that need something extra, like an admin-only check.

Both accept a single guard function or an array of guards, run in order, stopping at the first one that returns a redirect:

router.route("admin", "/admin", { guard: [requireAuth, requireAdmin] });

A guard returns a template id to redirect there, or nothing to let the navigation proceed, and can be async — useful for e.g. silently refreshing a session and skipping the login page if it succeeds:

async function requireAuth(templateId) {
  if (templateId === "login" && maybeHasSession()) {
    const ok = await tryRefresh();
    if (ok) return "welcome";
    return;
  }
  if (PROTECTED_PAGES.has(templateId) && !isAuthenticated()) return "login";
}

Use onGuardPending to show a spinner while an async guard is resolving.

API

  • createRouter(options): Router
  • router.route(templateId, path, { guard? }) — register a route's URL path and optional route-specific guard(s)
  • router.navigate(templateId, { push? }) — navigate, running guards and updating history
  • router.showPage(templateId) — render directly, bypassing guards
  • router.registerPageHandler(templateId, handler) — runs each time that template renders; independent of route() call order
  • router.templateForPath(path) — reverse lookup, falls back to notFoundId
  • router.start() — resolve and render the current URL; call once after registering routes and page handlers

See src/router.ts for the full RouterOptions/RouteOptions types.