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

@ash_rafhamid/crashlens-browser-sdk

v0.1.0

Published

Browser error reporting SDK for CrashLens

Readme

CrashLens browser SDK

The CrashLens browser SDK watches a web application for JavaScript failures and sends structured error events to a CrashLens API.

It captures uncaught errors and unhandled promise rejections automatically. Applications can also report caught exceptions manually. Each event may contain the stack trace, current page, release, environment, browser information, user ID, custom context, and recent click breadcrumbs.

Installation

Install the public package with:

npm install @ash_rafhamid/crashlens-browser-sdk

Setup

import CrashLens from "@ash_rafhamid/crashlens-browser-sdk";

CrashLens.init({
  apiKey: "cl_live_project_key",
  dsn: "https://your-crashlens-api.example",
  release: "1.4.0",
  environment: "production"
});

dsn may be the API origin or the complete /api/v1/events endpoint.

Add user and application context

CrashLens.setUser("customer-42");
CrashLens.setContext({ region: "BD", checkoutVersion: 3 });
CrashLens.addBreadcrumb("checkout", "Customer selected bKash");

Avoid sending passwords, access tokens, payment details, or other private data. The API redacts common sensitive key names, but applications should still collect only the context developers actually need.

Report a caught exception

try {
  await reserveInventory();
} catch (error) {
  const accepted = await CrashLens.captureException(error, {
    extra: { sku: "CLOUD-RUNNER-42" }
  });

  if (!accepted) {
    console.warn("CrashLens could not send the event");
  }
}

captureException never throws because monitoring should not break the monitored application. It returns true when the API accepts the event and false when reporting is unavailable.

Publishing

Build and test the workspace, review the package files, and publish it publicly.

cd packages/browser-sdk
npm run build
npm test
npm pack --dry-run
npm publish --access public

Never include the private CRASHLENS_ADMIN_KEY in this package or in browser code. A browser application receives only its project SDK key, which permits event ingestion but cannot read or manage issues.