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

buggerov

v1.0.0

Published

Lightweight, zero-config visual feedback and bug reporter widget.

Readme

Buggerov embeds a floating action button into your web app that lets clients or testers highlight bugs directly on the screen, write a description, and export a clean report with full browser metadata and console logs.


Features

  • 📸 On-screen Annotation: Highlight target bugs with simple drag-to-draw rectangle selectors.
  • 💻 Console Log Interceptor: Automatically captures console logs (console.log, warn, error, info) with proper error stack serialization.
  • 🚨 Global Exception Handling: Automatically captures unhandled exceptions and promise rejections.
  • 🌐 Network Request Sniffer: Monitors failed fetch and XMLHttpRequest calls (status codes $\ge 400$ or network drops) and logs them.
  • 🎨 Premium Aesthetic: Modern dark/light glassmorphic UI, responsive layouts, micro-animations, and a fullscreen screenshot lightbox.
  • 📝 Markdown Export: Direct markdown clipboard copying and local .md downloads containing all metadata and inline screenshots.
  • 🔗 Zero-config Webhooks: Automatically POSTs the structured report payload directly to any Slack, Discord, or custom webhook url.
  • 📋 Session Reports Dashboard: An in-widget dashboard containing all captured bug reports. Testers can copy/download individual reports, toggle developer log details, zoom screenshots, or batch export/clear reports.
  • 🔌 Offline / Webhook-free Mode: Run purely client-side! If no webhookUrl is provided, reports are accumulated in the session and can be manually exported by the tester.

Installation

Add Buggerov as a dependency to your project:

npm install buggerov

Quick Start

Import the library and call the initialization function in your entry file (e.g., main.ts or index.ts). Styles are bundled natively, so there is no need to import a separate stylesheet.

import { initBuggerov } from 'buggerov';

initBuggerov({
  webhookUrl: 'https://your-webhook-endpoint.com/api/feedback',
  enabled: true // Force enable (bypasses dev/staging environment checks)
});

How It Works (Auto-Enable Detection)

If the enabled field is not provided, Buggerov will auto-detect whether it should render based on the current context:

  • Checks if the bundler indicates a non-production build (process.env.NODE_ENV !== 'production' or Vite's import.meta.env.DEV).
  • Checks if the hostname is a local loopback address (localhost, 127.0.0.1, [::1], or .local).
  • Checks if the hostname contains common QA/staging keywords (e.g., dev, stage, staging, qa, test, preview, beta, sandbox).

Session Reports Dashboard & Offline Mode

When Buggerov is initialized, it displays a dual-button Floating Action Button (FAB) container:

  1. Report Bug Button (Left): Enters screenshot capture and annotation mode.
  2. Dashboard Button (Right): Circular button with a numeric red badge showing the count of bugs captured in the current session.

Offline and Local Storage Persistence

Captured reports are persisted in sessionStorage. This ensures that even if a tester navigates to another page, submits a form, or reloads the browser tab, the accumulated list of reports is preserved.

In-Widget Dashboard Features

Clicking the dashboard button opens the glassmorphic Session Reports manager containing:

  • Screenshot Lightbox: Click any screenshot thumbnail to open a fullscreen zoom overlay.
  • Inline Logs Inspecting: Click the Logs button on any card to toggle a code view of the captured logs for that specific bug.
  • Individual Operations: Copy markdown or download a .md file for any specific bug report.
  • Batch Operations: Copy all reports as a single combined markdown document, export/download all reports as a combined .md file, or clear all reports from the session storage.

API Reference

initBuggerov(config: BuggerovConfig)

Initializes the visual feedback widget and returns the BuggerovWidget instance (or null if disabled).

BuggerovConfig Options

| Property | Type | Default | Description | | :--- | :--- | :--- | :--- | | webhookUrl | string | undefined | URL where the JSON report payload will be POSTed. | | enabled | boolean \| (() => boolean) | Auto-detected | Overrides dev/staging detection checks. | | buttonText | string | "Report Bug" | Text label displayed on the floating action button. | | buttonPosition | 'bottom-right' \| 'bottom-left' \| 'top-right' \| 'top-left' | 'bottom-right' | Position of the floating button on the screen. | | customMetadata | Record<string, any> \| (() => Record<string, any>) | undefined | Additional variables to include in the report metadata. | | theme | 'light' \| 'dark' \| 'auto' | 'auto' | Color scheme for the feedback widget UI. | | maxLogs | number | 50 | Maximum number of console logs to preserve. | | customHeaders | Record<string, string> | undefined | Custom headers sent with the webhook POST request. | | onSuccess | () => void | undefined | Callback triggered after a successful report submission. | | onError | (error: Error) => void | undefined | Callback triggered if the webhook request fails. |


Webhook Payload Structure

When feedback is submitted, Buggerov sends a POST request containing a JSON body of type BuggerovPayload:

{
  "screenshot": "data:image/png;base64,iVBORw0KGgo...",
  "note": "The submit button has a weird alignment issue on mobile.",
  "metadata": {
    "url": "http://localhost:3000/",
    "title": "Buggerov Demo",
    "timestamp": "2026-05-28T21:13:30.000Z",
    "viewportWidth": 1280,
    "viewportHeight": 720,
    "screenWidth": 1920,
    "screenHeight": 1080,
    "userAgent": "Mozilla/5.0 ...",
    "os": "Windows",
    "browser": "Chrome",
    "logs": [
      {
        "type": "info",
        "message": "User action tracked. Current epoch time: 1779999934904",
        "timestamp": "2026-05-28T21:13:28.000Z"
      },
      {
        "type": "error",
        "message": "[Unhandled Exception] Error: AuthException: session expired",
        "timestamp": "2026-05-28T21:13:29.000Z"
      }
    ],
    "custom": {}
  }
}