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

@apica-io/apica-rum

v1.0.1

Published

RUM browser instrumentation scripts

Readme

Apica RUM implementation based on OTEL Browser SDK and Web Vitals.

The script instruments user interactions and web page behavior in both auto and manual mode. Emits the 3 Otel signals - Logs, Metrics and Traces. Any OTEL compatible endpoint that is reachable from the script can be used as sink endpoints. Script has been fined tuned for Ascent as backend.

  1. Build step

There are multiple ways to build the script as follows

a. Need to use a build tool like parcel to get the final script

npx parcel build apicarumwrapper.js --dist-dir dist --no-source-maps

b. Use the script commands available in package.json

npm run build

Minified RUM file will be available in the dist directory

This can then be added to a page as below.

This will launch auto instrumentation for the page and usage metrics will start ingestion, the script exposes the internal meters via returned object, this can be used to add custom meters e.g Business metrics of some kind

  1. Manual instrumentation

Internal meters corresponding to logs, metrics and traces used by the script are exposed via the returned object from the init call. These meters can be used to do custom instrumentation, for example some business metrics that is relevant for monitoring.

  1. Code structure

Code structure follows the three main signals - log.js, metric.js and trace.js These are used in ApicaRum.js apicarumwrapper.js is a wrapper for direct script import scenarios e.g script delivery via a CDN

  1. Packaging

Its possible to create a local package for distribution by executing

npm run pack

  1. Publish to npm

Package needs to be published under Apica account, this requires a npm user account under Apica. Need to login first and then publish

npm login

npm run publish