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

@errorgap/nextjs

v0.1.0

Published

Next.js SDK for Errorgap error tracking (client and server).

Readme

@errorgap/nextjs

Next.js SDK for Errorgap. It reports both server (Route Handlers, Server Components, middleware, server actions) and client (browser/React) errors, wiring @errorgap/node and @errorgap/browser into Next.js.

Works with the Next.js App Router (13.4+; onRequestError requires 15+).

Install

npm install @errorgap/nextjs

Configure

Set the connection env vars. The client build needs the NEXT_PUBLIC_ copies (the ingestion key is submit-only — safe in the browser, like a Sentry DSN):

# .env
ERRORGAP_ENDPOINT=https://errorgap.example.com
ERRORGAP_PROJECT_SLUG=my-project
ERRORGAP_API_KEY=flk_...

NEXT_PUBLIC_ERRORGAP_ENDPOINT=https://errorgap.example.com
NEXT_PUBLIC_ERRORGAP_PROJECT_SLUG=my-project
NEXT_PUBLIC_ERRORGAP_API_KEY=flk_...

Server errors — instrumentation.ts

// instrumentation.ts (project root or src/)
export { register, onRequestError } from "@errorgap/nextjs";

register() initializes the notifier at server startup; onRequestError (Next 15+) reports every unhandled server error with its route and method.

Client errors — instrumentation-client.ts

// instrumentation-client.ts (Next 15.3+)
import { initErrorgapClient } from "@errorgap/nextjs/client";

initErrorgapClient();

This hooks window errors and unhandled rejections with source-map-resolved stack traces.

React render errors — error.tsx / global-error.tsx

App Router error boundaries catch render errors that never reach window.onerror. Report them:

"use client";
import { useCaptureError } from "@errorgap/nextjs/react";

export default function GlobalError({ error, reset }: { error: Error; reset: () => void }) {
  useCaptureError(error);
  return (
    <html>
      <body>
        <button onClick={() => reset()}>Try again</button>
      </body>
    </html>
  );
}

Manual reporting

import { Errorgap } from "@errorgap/nextjs";        // server
// import { Errorgap } from "@errorgap/nextjs/client"; // client

await Errorgap.notify(error, { context: { component: "Checkout" } });

Notes

  • Server capture targets the Node.js runtime; it no-ops on the Edge runtime.
  • apiKey is an ingestion-only key and may be exposed via NEXT_PUBLIC_.

License

MIT.