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

@getoncall/next

v0.1.3

Published

OnCall error monitoring for Next.js (App Router).

Readme

@getoncall/next

npm install size license

Error monitoring for Next.js (App Router) — with plain-English diagnoses and verified fix PRs.

OnCall catches the errors your users hit, explains each in plain English, and — when you approve — opens a pull request that fixes the bug and confirms it held in production. This package wires the browser side into the App Router; pair it with @getoncall/node for route handlers and server actions.

Install — just ask your agent

In Cursor, Claude, Lovable, v0, or any AI editor, paste this (swap in your key):

Install OnCall in this Next.js app — add @getoncall/next and render <OnCallScript projectKey="onc_pk_your_project_key" /> in app/layout.tsx. Nothing else.

Connect the OnCall MCP server (npx @getoncall/mcp) and your agent installs and verifies it — client and server.

Install

npm install @getoncall/next

Add <OnCallScript /> to your root layout

// app/layout.tsx
import { OnCallScript } from "@getoncall/next";

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

That's the client side — uncaught errors, unhandled rejections, and console errors, with route + breadcrumb context.

Server side (route handlers, server actions)

Install @getoncall/node and init it once with your secret key:

import { initOncall, captureException } from "@getoncall/node";

initOncall({ key: process.env.ONCALL_SECRET_KEY! });

export async function POST(req: Request) {
  try {
    return await handle(req);
  } catch (err) {
    captureException(err, { route: "/api/checkout" });
    throw err;
  }
}

Keys

  • Browser — public project key onc_pk_… (safe to ship).
  • Server — secret key onc_sk_… from ONCALL_SECRET_KEY.

Both are on your project's install screen at intaglio.io.

Links

MIT © OnCall