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

@faurya/web

v0.1.0

Published

Browser-specific analytics implementation for Faurya SDK

Downloads

52

Readme

@faurya/web

Browser-specific analytics for the Faurya SDK.

Overview

@faurya/web provides browser adapters (localStorage, fetch), automatic SPA pageview tracking, singleton client management, browser metadata collection, environment guards, and cross-domain tracking helpers. It builds on @faurya/core.

Install

npm install @faurya/web

Usage

import { initFaurya, getFauryaClient } from '@faurya/web'

const client = await initFaurya({
  websiteId: 'my-site',
  autoCapturePageviews: true,
  allowLocalhost: true,  // optional: enable localhost tracking
})

client.track('click', { target: 'hero-cta' })

// Later, from any module:
const sameClient = getFauryaClient()

client.track('click', { target: 'hero-cta' }) queues a custom request body with browser metadata and:

extraData: {
  eventName: 'click',
  target: 'hero-cta',
}

Features

  • Auto-pageview tracking: Patches History API for SPA route changes
  • localStorage persistence: Visitor/session IDs survive page reloads
  • Singleton pattern: One client per app via initFaurya() / getFauryaClient()
  • Graceful fallback: Falls back to memory if localStorage is unavailable
  • Environment guards: Silently disables tracking on localhost, file://, iframes, bots
  • Cross-domain tracking: getTrackingParams() and buildCrossDomainUrl()
  • URL param restore: Reads visitor/session from URL on init, cleans up after
  • SSR-safe behavior: Returns a no-op client when browser globals are unavailable

Runtime Rules

  • Use @faurya/web for browser analytics.
  • In SSR/non-browser runtimes, initFaurya() returns a no-op client and does not start browser-only tracking.
  • Browser-only events include pageview, pageview_end, attention, DOM goals, and DOM scroll goals.

Configuration

| Option | Default | Description | |--------|---------|-------------| | allowLocalhost | false | Enable tracking on localhost | | allowIframe | false | Enable tracking in iframes | | allowedHostnames | undefined | Hostnames for cross-domain tracking |

License

MIT