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

@antonvishal/browserbase-tracking-kit

v0.1.0

Published

bbdash CLI and local dashboard for Browserbase tracking

Readme

@antonvishal/browserbase-tracking-kit

Early-stage, community-maintained software. Not affiliated with or endorsed by Browserbase.

Companion tooling for @antonvishal/browserbase-tracking: configuration loading, the bbdash CLI, and the bundled read-only local dashboard. It has no role in tracking writes and does not depend on the runtime package.

Requires Node.js 22+ or Bun 1.2+. The CLI shebang uses Node; Bun can still run bbdash through its Node-compatible path.

npm add -D @antonvishal/browserbase-tracking-kit
# or
bun add -d @antonvishal/browserbase-tracking-kit

Create browserbase.config.ts in the project root:

import { defineConfig } from "@antonvishal/browserbase-tracking-kit";

export default defineConfig({
  dbCredentials: {
    url: process.env.DATABASE_URL!,
  },
  dashboard: {
    port: 4321,
    open: true,
  },
});

Declare the documented tracking tables and views in your application's Drizzle schema, provision them through your application's migration workflow, then launch the dashboard. The runtime package ships the complete copyable schema at node_modules/@antonvishal/browserbase-tracking/examples/schema.ts:

npx bbdash dash
# or
bunx bbdash dash

Resolution order is --database-url, browserbase.config.ts, then DATABASE_URL. CLI options override config values:

--config <path>       Config file (default: browserbase.config.ts)
--database-url <url>  Override dbCredentials.url
--port <port>         Override dashboard.port
--no-open             Disable automatic browser opening

One process binds only to 127.0.0.1 and serves both the SPA and its validated, read-only /api/v1 HTTP interface. It validates the tracking schema version before listening; it never creates or migrates them.

The dashboard displays stored Search queries and results, Fetch URLs and content, response headers, and error details. Treat local access as access to the underlying tracking database. The server intentionally binds only to the loopback interface and has no authentication; do not proxy or expose it to a network.

License

MIT. Browserbase is a trademark of its respective owner; use of the name here only describes compatibility.