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

@sixtynine-digital/cms-tracking

v0.1.0

Published

Server-side, first-party event tracking client for SIXTYNINE CMS (Pulse analytics). Send page views and custom events from a Next.js (or any JS) backend — the delivery key never reaches the browser.

Readme

@sixtynine-digital/cms-tracking

Server-side, first-party event tracking for SIXTYNINE CMS (Pulse analytics).

Events are sent from your backend (Server Action / route handler / middleware) to the CMS. The browser only ever talks to your own origin, so the delivery key never ships to the client, and tracking is GDPR-friendly by design.

npm install @sixtynine-digital/cms-tracking

1. Create a tracker (server-only)

// lib/tracker.ts
import { createTracker } from "@sixtynine-digital/cms-tracking";

export const tracker = createTracker({
  apiKey: process.env.CMS_DELIVERY_KEY!, // a "delivery" key — keep it server-side
  baseUrl: process.env.CMS_BASE_URL!,    // e.g. https://cms.example.com/api/v1
});

2. First-party track route

// app/api/track/route.ts
import { createTrackHandler } from "@sixtynine-digital/cms-tracking/next";
import { tracker } from "@/lib/tracker";

export const POST = createTrackHandler({ tracker });

3. Automatic page views (Next 16)

// proxy.ts
import { NextResponse, type NextRequest, type NextFetchEvent } from "next/server";
import { trackPageView } from "@sixtynine-digital/cms-tracking/next";

export function proxy(request: NextRequest, event: NextFetchEvent) {
  const { pathname } = request.nextUrl;
  if (!pathname.startsWith("/_next") && !pathname.startsWith("/api")) {
    trackPageView(event, request);
  }
  return NextResponse.next();
}

export const config = { matcher: ["/((?!_next/static|_next/image|favicon.ico).*)"] };

4. Fire custom events

// app/actions/track.ts
"use server";
import { tracker } from "@/lib/tracker";

export async function trackAddToCart(itemId: string) {
  await tracker.track("add_to_cart", { item_id: itemId, price: 49 });
}

API

  • createTracker({ apiKey, baseUrl, debug? }) → Tracker
  • tracker.track(eventName, props?, ctx?)never throws; resolves void.
  • tracker.getEventSchema() — fetch the tenant's event catalog (throws on failure).
  • createTrackHandler({ tracker }) — a POST handler that always returns 202.
  • trackPageView(event, request, { endpoint? }) — fire-and-forget page view.

track and the handler swallow all errors so analytics can never break the host site. Set debug: true to log failures during development.