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

next-bugtracker

v1.0.0

Published

Next.js Bug Tracker Integration Package

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

pskthpskth

Keywords

Readme

next-bugtracker

A lightweight, developer-first Next.js bug reporting package that captures screenshots and environment metadata, processes reports using AI, and posts them directly to your GitHub repository as structured issues.

🚀 Installation & Local Usage

To use this local package in another project on your system, you can use any of the following methods. First, make sure you build the package in this directory:

npm run build

Method 1: Local Path Installation (Recommended)

In your destination Next.js project directory, install the package using its local file path:

npm install /home/pskth/projects/group2-bugtracker

Method 2: NPM Link

  1. In this package directory (/home/pskth/projects/group2-bugtracker), link the package:
    npm link
  2. In your destination Next.js project directory, connect to the link:
    npm link next-bugtracker

🛠️ Setup Wizard

Once installed in your destination project, run the setup wizard:

npx next-bugtracker init

The wizard will:

  1. Detect whether your project uses App Router or Pages Router (and if you use a src/ directory layout).
  2. Ask for your GitHub Owner/Repository.
  3. Ask for your AI Provider choice (OpenAI or Anthropic) and credentials.
  4. Automatically write next-bugtracker.config.ts to your project root.
  5. Populate .env.local with API keys and access tokens.
  6. Generate the /bug-report form route and its backend API endpoint.

📝 API Keys & Env Variables

The wizard writes the following to your destination project's .env.local:

  • BUGTRACKER_GITHUB_TOKEN: Your Personal Access Token or OAuth Token.
  • BUGTRACKER_AI_KEY: Your OpenAI or Anthropic API key.

Make sure .env.local is listed in your project's .gitignore to protect these tokens.

🎨 Neo Brutalist Bug Report Form

The form is accessible at /bug-report and has a premium Neo Brutalist theme using non-harsh colors.

  • Client Metadata Capture: Automatically captures OS, browser version, screen dimensions, current pathname, and submission timestamp on form submit.
  • Fail-Safe Processing: If your AI provider API key is not configured or the AI API call fails, the package will automatically fallback to generating a clean, unstructured issue on GitHub using raw input fields, ensuring you never lose a bug report.