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

@oleus/browser

v1.2.0

Published

Oleus browser observability SDK — CWV, JS errors, sessions, fetch instrumentation, session replay, feature flags, surveys, heatmaps

Readme

@oleus/browser

Browser RUM SDK for the Oleus platform — Core Web Vitals (LCP/CLS/FID/INP), JS errors with sourcemap symbolication server-side, fetch/XHR timing, sessions, and SPA route changes (works with Next.js client routing).

npm install @oleus/browser
import { init } from '@oleus/browser'

init({
  service:  'rondo-web',
  endpoint: 'https://api.dashboard.oleus.io/otlp',
  apiKey:   process.env.NEXT_PUBLIC_OLEUS_INGEST_KEY,  // per-app bearer key
  version:  process.env.NEXT_PUBLIC_VERCEL_GIT_COMMIT_SHA,  // release for sourcemaps
})

Identifying users

Every event carries a distinct_id. Before login it's a persisted anonymous id; call identify() after login to tie the anonymous history to the user — Oleus resolves both to one person.

import { getSDK } from '@oleus/browser'

const oleus = getSDK()

// after login
oleus.identify(user.id, { email: user.email, plan: user.plan })

// same person across devices (e.g. links a mobile session)
oleus.alias(mobileDistinctId)

// update person properties without changing identity
oleus.setPersonProperties({ plan: 'enterprise' })

// on logout — forget the user, start a fresh anonymous id + session
oleus.reset()

identify emits a $identify event containing the prior anonymous id, so pre-login pageviews/events stitch to the identified person. getDistinctId() returns the id currently being sent.

Migrating from setUser({ id, email, name })? It still works but is deprecated — it now forwards to identify(id, { email, name }).

Or via script tag (UMD build):

<script src="https://unpkg.com/@oleus/browser/dist/index.global.js"
        data-service="your-app-name" data-endpoint="https://api.dashboard.oleus.io/otlp"
        data-api-key="bik_live_YOUR_INGEST_KEY" defer></script>

Upload sourcemaps per deploy so minified stacks symbolicate:

curl -F "service=rondo-web" -F "release=$VERCEL_GIT_COMMIT_SHA" \
     -F "[email protected]/static/chunks/abc.js.map;filename=abc.js" \
     https://api.dashboard.oleus.io/api/symbols/sourcemaps