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

@alphatrait/react

v0.1.25

Published

Floating bug reporter UI for TesterKit — mounts the draggable bug icon, screenshots, and submit rail.

Readme

@alphatrait/react

Floating bug reporter UI for TesterKit — same draggable icon, action rail, screenshots, and submit flow as the stk demo.

BugKit.init() alone does not show any UI — you need this package.

Install

npm install @alphatrait/sdk@^0.1.2 @alphatrait/react@^0.1.2

Use published npm packages only. Do not create local shims named @alphatrait/react.

Styles

Bundled in v0.1.2+ — no Tailwind @source required on customer sites.

If the reporter looks unstyled:

// app/layout.tsx
import "@alphatrait/react/styles.css";

Environment

Ingest keys are publishable (browser-visible). All must be NEXT_PUBLIC_* in Next.js:

NEXT_PUBLIC_TESTERKIT_PROJECT_ID=your-project-id
NEXT_PUBLIC_TESTERKIT_API_URL=https://stk.alphatrait.com
NEXT_PUBLIC_ALPHA_STK_KEY=tk_...

Redeploy after changing env. Do not use ALPHA_STK_KEY alone (causes 401).

Next.js App Router

next.config.ts:

transpilePackages: ["@alphatrait/react", "@alphatrait/sdk"],

app/testerkit-provider.tsx:

"use client";

import { TesterKitReporter } from "@alphatrait/react";

export function TesterKitProvider({ children }: { children: React.ReactNode }) {
  return (
    <>
      <TesterKitReporter
        projectId={process.env.NEXT_PUBLIC_TESTERKIT_PROJECT_ID}
        apiKey={process.env.NEXT_PUBLIC_ALPHA_STK_KEY}
        apiBaseUrl={process.env.NEXT_PUBLIC_TESTERKIT_API_URL}
      />
      {children}
    </>
  );
}

app/layout.tsx:

import { TesterKitProvider } from "./testerkit-provider";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        <TesterKitProvider>{children}</TesterKitProvider>
      </body>
    </html>
  );
}

Read env in your provider file so Next.js inlines values at build time.

Do not call BugKit.init() separately.

Full checklist: docs/CUSTOMER-INTEGRATION.md (monorepo) or stk admin Generate key copy blocks.