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

@crxlens/sdk

v0.1.1

Published

Observability SDK for Chrome Extensions — capture errors, breadcrumbs, and cross-context traces.

Readme

@crxlens/sdk

The official JavaScript SDK for CRXLens — an observability platform for Chrome Extensions.

Capture errors, breadcrumbs, and cross-context execution traces across your extension's background service worker, content scripts, and popup UI.


Installation

npm install @crxlens/sdk

Quick Start

Call init() at the top of each extension context that you want to monitor (background, content, and popup).

import { CRXLens } from '@crxlens/sdk';

CRXLens.init({
  apiKey: 'YOUR_PROJECT_API_KEY'
});

Your API key is available from the CRXLens Dashboard.


Usage

Initialize

import { CRXLens } from '@crxlens/sdk';

CRXLens.init({
  apiKey: 'your-api-key',
  // Optional: override the default endpoint (useful for self-hosting)
  endpoint: 'https://crxlens.io/api/ingest'
});

Set User Context

Attach the current user to all subsequent events for easier debugging.

CRXLens.setUser({
  id: 'user_123',
  email: '[email protected]',  // optional
  username: 'johndoe'         // optional
});

Set Custom Tags

Add key/value metadata to all events from this context.

CRXLens.setTags({
  plan: 'pro',
  environment: 'production'
});

Set Extra Data

Attach arbitrary extra payload to events.

CRXLens.setExtra({
  featureFlags: { darkMode: true }
});

Capture Exceptions Manually

try {
  riskyOperation();
} catch (err) {
  CRXLens.captureException(err);
}

Capture Messages

CRXLens.captureMessage('User clicked the reset button');

How It Works

The SDK hooks into each extension context independently and automatically:

| Feature | Details | |---|---| | Error Capture | Intercepts window.onerror, unhandledrejection, and self errors for Service Workers | | Breadcrumbs | Monkey-patches console.log/warn/error and fetch to maintain a circular buffer of the last 100 actions | | Cross-Context Tracing | Intercepts chrome.runtime.sendMessage and chrome.tabs.sendMessage to automatically inject and propagate trace_id values | | Offline Queue | Events are persisted to chrome.storage.local and re-sent when connectivity is restored | | Environment Metadata | Automatically detects execution_context (background / content_script / popup / options), extension_id, extension_version, and chrome_version |


Manifest V3 Permissions

Add the following to your manifest.json:

{
  "permissions": ["storage"],
  "host_permissions": [
    "https://crxlens.io/*"
  ]
}

Example: Full Setup

background.js

import { CRXLens } from '@crxlens/sdk';

CRXLens.init({ apiKey: 'YOUR_KEY' });
CRXLens.setTags({ context: 'background' });

content.js

import { CRXLens } from '@crxlens/sdk';

CRXLens.init({ apiKey: 'YOUR_KEY' });
CRXLens.setUser({ id: currentUserId });

popup.js

import { CRXLens } from '@crxlens/sdk';

CRXLens.init({ apiKey: 'YOUR_KEY' });

License

MIT