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

@feedbakkr/watch-ui

v0.2.3

Published

React components for browsing and acting on errors collected by a Feedbakkr Watch worker.

Readme

@feedbakkr/watch-ui

React components for browsing and acting on errors collected by a Feedbakkr Watch worker. Designed to be embedded inside the Feedbakkr dashboard, but usable in any React app that injects an apiClient.

pnpm add @feedbakkr/watch-ui

React 18 or 19 is a peer dependency. Tailwind CSS is assumed in the host app (class names are inline). If you need scoped styles, fork or wrap.

What it exports

Pages

  • <ErrorGroupsPage projectId connectionId apiClient onSelectGroup? /> — list view with filters, sort, and click-through.
  • <ErrorGroupDetailPage groupId apiClient onBack? /> — detail view with occurrence history and resolve / ignore / reopen actions.
  • <ErrorOverviewCards projectId? environment? apiClient /> — three-card summary for a dashboard tile.

Primitives

  • <ErrorSeverityBadge severity />
  • <ErrorStatusBadge status />
  • <ErrorStackTrace stack />
  • <ErrorOccurrenceList occurrences onSelect? />
  • <ErrorGroupRow group onSelect? />
  • <ErrorFilters value onChange />

API client

  • ToolApiClient — interface every page consumes. The dashboard injects its own implementation that proxies through a BFF, so the worker key never reaches the browser.
  • createBrowserApiClient({ baseUrl, getKey }) — reference impl that calls the worker directly. Useful for local dev / standalone use.

Wiring

import { ErrorGroupsPage, createBrowserApiClient } from "@feedbakkr/watch-ui";

const apiClient = createBrowserApiClient({
	baseUrl: connection.apiBaseUrl,
	getKey: () => Promise.resolve(connection.apiKey),
});

<ErrorGroupsPage
	projectId={project.id}
	connectionId={connection.id}
	apiClient={apiClient}
	onSelectGroup={(group) => router.push(`/errors/${group.id}`)}
/>;

For production use inside Feedbakkr, build your own apiClient that hits your dashboard's BFF and let the BFF attach the tool key server-side.

Boundaries

The UI package does not own:

  • routing
  • Feedbakkr auth or session
  • the dashboard's app shell or layout
  • project selection or global navigation

Feedbakkr — or whatever host renders these components — owns all of that.

See also