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

index-site

v0.1.24

Published

Reusable React application for a filesystem-backed index site.

Readme

index-site

Reusable React application for a filesystem-backed index site.

The consuming client calls startIndexSite() and provides three files in its public directory:

  • index.site.json configures site-level behavior, including language, typography, map access, feature flags, and data paths.
  • index.language.json contains all user-facing copy, menu/filter labels, calendar messages, event-detail labels, and interpolated templates such as {count} and {date}.
  • index.data.json contains the root data set.

Data routing follows the URL. / and /items/:itemId load /index.data.json. Any other content path loads its own nested file, so /one/yes and /one/yes/items/:itemId load /one/yes/index.data.json. View suffixes such as /map and /calendar also keep the current content path.

dataPaths can override the convention with exact site-path mappings:

{
  "language": "en",
  "isRtl": false,
  "dataPaths": {
    "/one/yes": "/custom/one-yes.json"
  }
}

Site typography

Typography belongs to the site configuration:

{
  "typography": {
    "bodyFontFamily": "\"Open Sans\", sans-serif",
    "headingFontFamily": "\"Open Sans\", sans-serif",
    "googleFontsUrl": "https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&display=swap"
  }
}

index-site applies the font stacks through CSS variables and loads the Google Fonts stylesheet when needed. A client may include the same stylesheet URL in index.html with preconnect/preload hints; the runtime detects the matching stylesheet and does not add a duplicate.

Keep each site's request script-specific. For example, Setúbal requests only Open Sans, while Tel Aviv requests the Hebrew-capable Rubik and Secular One families.

Maps and feature flags

The Google Maps browser key and lightbox behavior also belong to the site configuration:

{
  "features": {
    "lightboxDetails": true,
    "lightboxDetailsMobile": true
  },
  "map": {
    "apiKey": "YOUR_RESTRICTED_BROWSER_MAPS_KEY",
    "center": {
      "lat": 38.35,
      "lng": -8.85
    },
    "zoom": 9
  }
}

Both lightbox flags default to true. Restrict the browser map key to the required Google Maps APIs and deployed site origins.