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

@glossia/web

v0.1.0

Published

Cookieless, privacy-friendly web analytics that surfaces localization opportunities for Glossia.

Readme

@glossia/web

Cookieless, privacy-friendly web analytics that surfaces localization opportunities. Add one line of HTML and Glossia shows you which languages and countries your visitors actually want, and where you have a localization gap.

  • No cookies, no fingerprinting. Nothing is stored on the visitor's device. Unique visitors are derived server-side from a daily-rotated hash that cannot be linked across days.
  • Localization-first. Collects browser languages, country (GeoIP), referrer, and the pages underserved traffic lands on, so you can prioritize the next locale with data.
  • Tiny. One small script, no dependencies, ships via sendBeacon.

Install

Snippet (no build step)

Add this to your site:

<script defer data-domain="example.com" src="https://cdn.glossia.ai/web.js"></script>

The script auto-initializes and records pageviews, including on client-side navigation (single-page apps). data-domain is optional — when omitted, the SDK uses window.location.hostname to identify the project. Point data-endpoint at a self-hosted collect host if you don't use the Glossia CDN.

npm

npm install @glossia/web
import glossia from "@glossia/web";

glossia.init();

// Record a custom event:
glossia.track("signup");

domain is inferred from window.location.hostname. Pass { domain: "example.com" } to override, for example to send events from a staging origin to the same project as production.

What gets collected

Sent from the browser: page URL, referrer, navigator.languages, timezone, screen width, and a per-tab session id (in sessionStorage, cleared on close).

Derived on the server (never stored raw): a daily-rotated visitor id, country from GeoIP, device/browser/OS from the User-Agent, and the localization gap against your project's target languages.

License

MIT