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

@volatodev/nextjs

v0.1.0-beta.0

Published

Next.js error tracking SDK — captures errors across all Next.js runtimes and streams them to Volato.

Readme

@volatodev/nextjs

Next.js error-tracking SDK for Volato — agent-native error tracking.

Captures errors across every Next.js runtime (Node, Edge, browser) and streams them to your Volato project, where your AI agent reads them back with full fix context. Requires Next.js 15+ (App Router).

Privacy: your source code never leaves your machine. Uploaded sourcemaps have sourcesContent stripped client-side; the agent reads the snippet from your own repo. Request bodies, cookies, and auth headers are never captured.

Quickstart

npm install @volatodev/nextjs
npm install -g @volatodev/cli
volato init                 # wires the SDK into your app
volato login <token>        # workspace token from https://app.volato.dev

volato init writes the DSN, creates instrumentation.ts, mounts the browser bootstrap, and sets up the tunnel route. If you'd rather wire it by hand, follow the steps below.

Manual setup

1. Set your DSN in .env.local:

NEXT_PUBLIC_VOLATO_DSN="https://<public_key>@ingest.volato.dev/<project_id>"

NEXT_PUBLIC_* is readable on the server too, so this single var covers every runtime.

2. Server, RSC & route-handler capture — re-export the hook from instrumentation.ts:

export { onRequestError } from "@volatodev/nextjs/instrumentation";

3. Browser capture — mount the bootstrap in your root layout:

import { VolatoBootstrap } from "@volatodev/nextjs/client";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html>
      <body>
        <VolatoBootstrap dsn={process.env.NEXT_PUBLIC_VOLATO_DSN!} />
        {children}
      </body>
    </html>
  );
}

4. Render-phase errors — capture from the App Router's app/error.tsx boundary:

"use client";

import { useEffect } from "react";
import { captureFromErrorBoundary } from "@volatodev/nextjs/error-boundary";

export default function Error({ error, reset }: { error: Error & { digest?: string }; reset: () => void }) {
  useEffect(() => { captureFromErrorBoundary(error); }, [error]);
  return <button onClick={reset}>Try again</button>;
}

5. Edge middleware (optional):

import { wrapMiddleware } from "@volatodev/nextjs/middleware";

export default wrapMiddleware(async (req) => {
  // your existing middleware logic
}, { dsn: process.env.NEXT_PUBLIC_VOLATO_DSN! });

6. Same-origin tunnel (optional, sidesteps adblockers) — volato init creates this at app/monitoring/route.ts:

import { createTunnelHandler } from "@volatodev/nextjs/server";

export const POST = createTunnelHandler();

Sourcemap upload (readable stack traces)

Wrap your next.config so the build uploads sourcesContent-stripped maps:

import { withVolato } from "@volatodev/nextjs";

export default withVolato({
  // your Next.js config
});

Breadcrumbs

Once VolatoBootstrap is mounted, opt into automatic context (silent until called):

"use client";
import { useEffect } from "react";
import { instrumentFetch, instrumentNavigation, instrumentConsole } from "@volatodev/nextjs/client";

useEffect(() => {
  instrumentFetch();        // failed fetches
  instrumentNavigation();   // pushState / popstate
  instrumentConsole();      // console.error (filters React noise by default)
}, []);

Push your own anytime:

import { addBreadcrumb } from "@volatodev/nextjs/client";
addBreadcrumb({ category: "auth", message: "user signed in", data: { userId } });

Configuration

Every runtime entry accepts a VolatoConfig:

{
  dsn: string;
  environment?: string;       // "development" no-ops; defaults to NODE_ENV
  release?: string;           // git SHA / semver; auto-detected from VOLATO_RELEASE
  beforeSend?: (event) => event | null;   // mutate or drop events (PII scrubbing)
  ignoreErrors?: (string | RegExp)[];     // silence known noise by type/message
  tunnel?: string | false;    // same-origin tunnel path; defaults to "/monitoring"
}

beforeSend runs once per event right before send. Throwing inside it never crashes your app — the event is sent through unchanged.

License

MIT © Wrenchy SASU