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

@addilytics/wintercg

v0.0.1

Published

Addilytics server capture and bundled browser relay for WinterCG handlers.

Readme

@addilytics/wintercg

Wraps Web Request handlers, including Cloudflare Workers, Deno, Bun, and edge runtimes. The wrapper preserves the handler's argument tuple, whether it receives one argument or several.

import { withAddilytics } from '@addilytics/wintercg';

export default {
	fetch: withAddilytics(handler, {
		endpoint: 'https://addilytics.example',
		siteKey: 'ak_...'
	})
};

For a runtime that stores its scheduler somewhere other than the handler arguments, pass a resolver:

const wrapped = withAddilytics(handler, {
	endpoint: 'https://addilytics.example',
	siteKey: 'ak_...',
	waitUntil: (platform) => platform.context.waitUntil.bind(platform.context)
});

The default server mode counts only requests that execute this handler. For an application with a client router, use the tracker from addilytics/browser in the router's committed-navigation hook. The tracker is compiled into your application and posts to the relay owned by the wrapper. There is no hosted script and the site key stays in server code.

const analytics = withAddilytics(handler, {
	endpoint: 'https://addilytics.example',
	mode: 'client',
	siteKey: env.ADDILYTICS_KEY
});
import { createBrowserTracker } from '@addilytics/wintercg/browser';

const tracker = createBrowserTracker({ mode: 'client' });
void tracker.pageview();
export const trackCommittedNavigation = (url: URL, key: string) =>
	tracker.pageview(url, { navigationKey: key });
window.addEventListener('pageshow', (event) => {
	if (event.persisted) void tracker.pageview(location.href, { force: true });
});

Call trackCommittedNavigation from the router's official post-navigation hook. Do not treat a loader, prefetch, or data request as a navigation.

client mode disables automatic document pageviews and lets the browser count the initial load, so prerendered pages and CDN hits are covered. Use hybrid on both sides when every initial document reaches the server. Hybrid mode keeps the server pageview and skips the browser's first callback. Hash-only changes are ignored unless trackHashChanges is true. If you change the browser endpoint, set the same path as relayPath on the wrapper.