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

@claria-analytics/web

v0.1.1

Published

Claria client-side analytics tracker

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

pabloomvcpabloomvc

Keywords

Readme

@claria-analytics/web

Client-side analytics for tracking how human visitors interact with your website. Part of the Claria analytics platform.

What it does

@claria-analytics/web tracks page views from real human visitors. It fires on every page navigation, capturing the URL, referrer, and a first-party session identifier. Data is sent to the Claria backend for analysis alongside AI bot traffic.

Key characteristics:

  • Lightweight -- no dependencies, minimal footprint
  • Uses navigator.sendBeacon for reliable delivery (with fetch fallback)
  • First-party session cookie (7-day default, configurable)
  • SSR-safe -- guards against window/document access during server rendering
  • Never throws -- all errors are silently caught to avoid impacting your site

Installation

npm install @claria-analytics/web
pnpm add @claria-analytics/web
yarn add @claria-analytics/web

Quick Start (Next.js + React)

Add ClariaAnalytics to your root layout. It renders nothing visible -- it only fires analytics events on route changes.

// app/layout.tsx
import { ClariaAnalytics } from "@claria-analytics/web/react";
import { Suspense } from "react";

export default function RootLayout({
  children,
}: {
  children: React.ReactNode;
}) {
  return (
    <html lang="en">
      <body>
        <Suspense fallback={null}>
          <ClariaAnalytics
            clientId={process.env.NEXT_PUBLIC_CLARIA_CLIENT_ID!}
          />
        </Suspense>
        {children}
      </body>
    </html>
  );
}

Why <Suspense>? The ClariaAnalytics component uses useSearchParams() internally, which requires a Suspense boundary in the Next.js App Router.

Framework-Agnostic Usage

If you're not using React, you can call sendPageView directly:

import { sendPageView } from "@claria-analytics/web";

sendPageView({ clientId: "your_client_id" });

Call this on every page navigation in your app (e.g., after a popstate event or route change).

Configuration

All configuration is passed via props (React) or the config object (core API).

| Prop / Field | Type | Required | Default | Description | | ------------ | --------- | -------- | ------------------------------------- | -------------------------------------------------- | | clientId | string | Yes | -- | Your Claria client identifier (provided by Claria) | | endpoint | string | No | https://claria-dashboard.vercel.app | Claria backend URL | | sessionTTL | number | No | 604800 (7 days) | Session cookie lifetime in seconds | | debug | boolean | No | false | Enable debug logging to the browser console |

Exports

| Entry Point | Export | Description | | ----------------------------- | ----------------- | -------------------------------------- | | @claria-analytics/web | sendPageView | Framework-agnostic page view function | | @claria-analytics/web/react | ClariaAnalytics | React component for Next.js App Router |

Types

Both entry points also export the following TypeScript types:

  • ClariaWebConfig -- Configuration object shape
  • PageViewPayload -- The payload sent to the Claria backend
  • ClariaAnalyticsProps -- React component props (same as ClariaWebConfig)

How It Works

  1. On each page navigation, the SDK reads (or creates) a claria_sid session cookie.
  2. It builds a minimal payload: client_id, url, referrer, session_id, and a timestamp.
  3. The payload is sent to {endpoint}/api/collect via sendBeacon (or fetch as fallback).
  4. All parsing, attribution, and verification happens on the Claria backend -- the SDK is a lightweight data forwarder.

License

Proprietary. All rights reserved.