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

@dcl/analytics-component

v1.0.6

Published

Analytics component for core components library

Readme

Analytics Component (@dcl/analytics-component)

A component for sending analytics events to an external API.

Features

  • Send analytics events with environment and service context
  • Error handling and logging
  • Configurable request timeout
  • Fire-and-forget or awaited delivery modes

Configuration

The component reads the following environment variables via the config component:

| Variable | Required | Description | | --- | --- | --- | | ANALYTICS_API_URL | yes | Endpoint that receives the POSTed events. | | ANALYTICS_API_TOKEN | yes | Token sent in the x-token header. | | ANALYTICS_CONTEXT | yes | Context value included with every event (e.g. service name). | | ENV | yes | Environment name injected into each event body. | | ANALYTICS_REQUEST_TIMEOUT | no | Request timeout in ms. Defaults to 10000. |

Usage

import { createAnalyticsComponent } from '@dcl/analytics-component'

type Events = {
  user_login: { userId: string; timestamp: number }
}

const analytics = await createAnalyticsComponent<Events>({
  fetcher,
  logs,
  config
})

// Await delivery (errors are logged, never thrown):
await analytics.sendEvent('user_login', { userId: '123', timestamp: Date.now() })

// Fire-and-forget:
analytics.fireEvent('user_login', { userId: '123', timestamp: Date.now() })

Note: the caller's body is merged with { env }, so env is a reserved key and will be overwritten if passed.