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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@bugbybug/vue

v0.1.1

Published

Official Vue.js SDK for BugByBug

Readme

@bugbybug/vue

The official Vue.js SDK for BugByBug. It wraps @bugbybug/browser to provide framework-specific error handling, capturing component names, lifecycle hooks, and optional props data.

Installation

npm install @bugbybug/vue

Usage

Initialize the SDK in your main application file (e.g., main.js or main.ts).

import { createApp } from 'vue';
import App from './App.vue';
import { BugByBug } from '@bugbybug/vue';

const app = createApp(App);

app.use(BugByBug, {
  apiKey: 'YOUR_PROJECT_API_KEY', // Starts with bbb_
  environment: 'production',
  trackProps: false // Optional: set to true to include component props in error reports
});

app.mount('#app');

Composition API (useBugByBug)

You can access the BugByBug client inside your components using the useBugByBug composable.

<script setup>
import { useBugByBug } from '@bugbybug/vue';

const bbb = useBugByBug();

const handleRisk = () => {
  try {
    throw new Error("Something went wrong!");
  } catch (e) {
    bbb.captureException(e, { customTag: 'checkout-flow' });
  }
};
</script>

Options API ($bugbybug)

For legacy components using the Options API, the client is available globally as $bugbybug.

export default {
  methods: {
    saveData() {
      try {
        // logic
      } catch (error) {
        this.$bugbybug.captureException(error);
      }
    }
  }
}

What gets captured?

When a Vue error occurs (e.g., inside a component lifecycle hook or a template), @bugbybug/vue automatically captures:

The Error: Stack trace and message.

Component Name: The name of the component where the error originated.

Lifecycle Hook: The stage (e.g., mounted, created) where the crash happened.

Source File: The file path of the component (in development mode).

Standard Context: Browser, OS, URL, User Session (inherited from the core SDK).