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

@ishaqyusuf/logly-core

v0.2.0

Published

Privacy-safe browser analytics contracts, durable delivery, and batching for Logly.

Readme

@ishaqyusuf/logly-core

Framework-independent contracts and browser client for a deliberately small Logly integration: one visitor-day, automatically discovered events, bounded properties, and durable batched same-origin delivery.

bun add @ishaqyusuf/logly-core
import { createAnalytics } from "@ishaqyusuf/logly-core";

const analytics = createAnalytics({
  project: "afterservice",
  endpoint: "/api/analytics",
  permission: () => "allowed",
});

analytics.init();
analytics.track("cta_clicked", { cta: "join_beta" });
analytics.trackPageView({ route: "/pricing" });

The project supplies the permission decision. Permission must be allowed before the client creates or reads its project-scoped local visitor ID. The first-ever visitor event is delivered immediately. Later visits and events are queued in IndexedDB and flush after 60 seconds, at 25 events, at 48 KiB of queued payload, on page lifecycle changes, or when connectivity returns. Failed batches retain their original event IDs for idempotent retry and are removed only after a 2xx collector response.

The queue defaults to 250 events retained for 24 hours. Override flushIntervalMs, flushAt, maxQueueEvents, or maxQueueAgeMs at initialization when an integration needs stricter limits. Local storage is used only for the small project-scoped visitor record; cookies are not used.