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

patchly

v0.2.2

Published

AI-powered error tracking SDK for browser and Node.js

Readme

Patchly SDK

Capture browser and Node.js runtime errors and send them to Patchly.

Install

npm install patchly

Quick Start

import { init } from "patchly";

const patchly = init({
	dsn: process.env.NEXT_PUBLIC_PATCHLY_DSN,
	release: process.env.VERCEL_GIT_COMMIT_SHA,
});

init() is safe to call during builds. If dsn is missing, the SDK logs a warning and no-ops.

Manual Capture

import { captureError, flush } from "patchly";

try {
	await runJob();
} catch (error) {
	captureError(error instanceof Error ? error : new Error(String(error)));
	await flush();
	throw error;
}

Use flush() in serverless request hooks, route handlers, or jobs that may finish before the normal batch interval.

Next.js App Router

Use Next.js onRequestError to capture errors that Next catches and turns into 500 responses.

import type { Instrumentation } from "next";

let patchly: ReturnType<typeof import("patchly").init> | null = null;

async function getPatchly() {
	if (process.env.NEXT_RUNTIME !== "nodejs" || !process.env.PATCHLY_DSN) return null;
	if (patchly) return patchly;

	const { init } = await import("patchly");
	patchly = init({
		dsn: process.env.PATCHLY_DSN,
		release: process.env.VERCEL_GIT_COMMIT_SHA,
	});
	return patchly;
}

export async function register() {
	await getPatchly();
}

export const onRequestError: Instrumentation.onRequestError = async (error) => {
	const client = await getPatchly();
	if (!client) return;

	client.capture(error);
	await client.flush();
};

Breadcrumbs

import { addBreadcrumb } from "patchly";

addBreadcrumb({
	category: "checkout",
	message: "User submitted payment form",
	level: "info",
	data: { plan: "pro" },
});

React Error Boundary

import { PatchlyErrorBoundary } from "patchly/react";

export function App() {
	return (
		<PatchlyErrorBoundary fallback={<p>Something went wrong.</p>}>
			<Routes />
		</PatchlyErrorBoundary>
	);
}

Configuration

init({
	dsn: process.env.NEXT_PUBLIC_PATCHLY_DSN,
	release: "[email protected]",
	userId: "user_123",
	autoCapture: true,
	captureConsoleErrors: true,
	captureNetworkErrors: true,
	enableBreadcrumbs: true,
	maxBreadcrumbs: 20,
});

The SDK automatically captures unhandled errors, unhandled promise rejections, console.error calls, failed fetch/XHR requests, and breadcrumbs. Requests to Patchly ingest endpoints are excluded to avoid feedback loops. Sensitive URL query values such as token, code, password, secret, and api_key are redacted before network events are sent.

Links

  • Docs: https://patchly.cc/docs
  • Dashboard: https://patchly.cc
  • Issues: https://github.com/tooyipjee/patchly/issues