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

@bugstate/js-sdk

v1.0.2

Published

JavaScript SDK for BugState Error Monitoring Service

Readme

@bugstate/js-sdk

JavaScript SDK for BugState Error Monitoring Service.

Install

  • From npm:
npm install @bugstate/js-sdk
  • Or install locally during development:
# from the package root
npm link
# in your project
npm link @bugstate/js-sdk

Quick Start

Choose the import style that matches your project.

  • ESM (modern):
import BugState from '@bugstate/js-sdk';

const bs = new BugState({ apiKey: process.env.BUGSTATE_API_KEY });
bs.init();

// capture an error
try {
  throw new Error('Test error');
} catch (err) {
  bs.capture(err);
}
  • CommonJS (Node.js / older bundlers):
const BugState = require('@bugstate/js-sdk').default || require('@bugstate/js-sdk');

const bs = new BugState({ apiKey: process.env.BUGSTATE_API_KEY });
bs.init();
bs.capture(new Error('Test error'));
  • TypeScript usage:
import BugState from '@bugstate/js-sdk';

const bs = new BugState({ apiKey: process.env.BUGSTATE_API_KEY });
bs.init();

// bs has TypeScript types emitted to `dist/index.d.ts`

Configuration Options

Pass an options object to the constructor. Typical options:

  • apiKey (string) — Your BugState project API key.
  • environment (string) — e.g. production, staging.
  • release (string) — application release/version.

Example:

const bs = new BugState({
  apiKey: 'your-key',
  environment: 'production',
  release: '1.2.3'
});

API Reference

This README gives integration examples only. For full API details, see the source:

Common methods you can expect:

  • init() — initialize the SDK and start automatic capture hooks
  • capture(error) — send an Error object or message to BugState
  • configure(opts) — update SDK configuration at runtime

(Check src/index.ts for exact method names and signatures.)

Build & Publish

This package uses TypeScript. Build before publishing:

npm run build

prepublishOnly already runs the build, but running it locally is recommended.

Support

Open issues on the repository or contact the package author.