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

@sursaut/kit

v0.1.0

Published

Routing, i18n, and application utilities for Sursaut

Readme

@sursaut/kit

Application-level toolkit for Sursaut apps — reactive client state, routing, API client, CSS injection, localStorage persistence, and Intl formatting.

Entry Points

| Import | Purpose | |--------|---------| | @sursaut/kit | Auto-selects DOM (browser) or Node (SSR) | | @sursaut/kit/dom | Browser: real DOM listeners, fetch API, stored() | | @sursaut/kit/node | Node: ALS-backed request context, file-based routing helpers, storage stub | | @sursaut/kit/intl | Intl formatting components (separate entry) |

Quick Start

import { client, Router, css } from '@sursaut/kit'

const routes = [
  { path: '/', view: () => <h1>Home</h1> },
  { path: '/about', lazy: () => import('./about').then((mod) => mod.default) },
]

function App() {
  return <>
    <nav>
      <button onClick={() => client.navigate('/')}>Home</button>
      <button onClick={() => client.navigate('/about')}>About</button>
    </nav>
    <Router
      routes={routes}
      loading={({ route }) => <p>Loading {route.path}…</p>}
      notFound={() => <h1>404</h1>}
    />
  </>
}

Features

  • Reactive client — URL, viewport, focus, visibility, language, timezone, direction, online, prefersDark
  • Router[param:format], [...catchAll], optional query params, custom format registry, lazy route modules with route-level loading/error UI and link-driven module prefetch
  • API client — interceptors, SSR hydration, middleware, retry, short-lived shared GET prefetch via prefetch()
  • CSS injectioncss/sass/scss template tags, SSR collection
  • Head management<Head> and useHead() with additive DOM mounting and SSR collection through board
  • localStoragestored() with inter-tab sync and reactive cleanup
  • Intl<Number>, <Date>, <RelativeTime>, <List>, <Plural>, <DisplayNames> from @sursaut/kit/intl

Head Management

import { Head } from '@sursaut/kit'

function App() {
  return <>
    <Head>
      <title>Sursaut App</title>
      <link rel="canonical" href="https://example.com/app" />
    </Head>
    <main>...</main>
  </>
}
  • <Head> mounts additive content into document.head in the browser
  • useHead() exposes the same behavior imperatively and returns a cleanup function
  • during board SSR, collected head HTML is injected into the final <head> together with hydration payloads
  • do not use latch(document.head, ...) for kit head management; latch() owns and replaces the whole target

Intl Entry

Intl intentionally stays on @sursaut/kit/intl rather than the shared kit barrel.

  • it is an optional subsystem
  • it is cross-environment, not part of the platform bootstrap surface
  • consumers that only want Intl formatting should not import the rest of kit's app/runtime entry by accident

Documentation

See docs/ for full guides.

License

MIT