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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@bharathvaj/fullstory-bugsnag

v1.1.0

Published

Fullstory Bugsnag Integration

Downloads

3

Readme

fullstory-bugsnag

The FullStory-Bugsnag integration seamlessly integrates the FullStorys and Bugsnag platforms. When you look at a browser error in Bugsnag, you will see a link to the FullStory session replay at that exact moment in time. When you are watching a FullStory replay and your user experiences an error, you will see a custom error with the basic error details.

Table of content

Pre-Requisites

For the FullStory-Bugsnag integration to work, you must have the FullStory browser SDK package and the Bugsnag browser SDK package.

Installation

To install the stable version:

with npm:

npm install --save @bharathvaj/fullstory-bugsnag

with yarn:

yarn add @bharathvaj/fullstory-bugsnag

Setup

Code Changes

To set up the integration, both FullStory and Bugsnag need to be initialized. Please add the following code:

import Bugsnag from '@bugsnag/js';
import * as FullStory from '@fullstory/browser';
import BugsnagFullStory from '@bharathvaj/fullstory-bugsnag';

FullStory.init({ orgId: '__FULLSTORY_ORG_ID__' });

Bugsnag.start({
  apiKey: '__YOUR_API_KEY__',
  plugins: [new BugsnagFullStory(options)],
  // ...
});

Replace __YOUR_API_KEY__ with the API found in Project Settings.

You also need to replace __FULLSTORY_ORG_ID__ with the value of _fs_org in the FullStory recording snippet on your FullStory settings page.

Options

You can also customize the error event name in FullStory by

// ...
Bugsnag.start({
  apiKey: '__YOUR_API_KEY__',
  plugins: [
    new BugsnagFullStory({
      fsEventName: 'Custom Error Name',
    }),
  ],
  // ...
});

//...

Roadmap

[ ] - Support Bugsnag Error link in FullStory Custom Event.

[ ] - Add Unit test cases

[ ] - ~~Register this integration as plugin to bugsnap core library~~

How it works

In Bugssnag, you should see additional tab called FULLSTORY for the error event which will have urlAtTime.

BugSnag

In FullStory, you should see an event called BugSnag Error on the right sidebar.

FullStory