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

@upgoose/cloudflare

v0.1.0

Published

Upgoose error tracking for Cloudflare Workers and other edge runtimes

Readme

@upgoose/cloudflare

Error tracking for Cloudflare Workers and other edge runtimes, from Upgoose.

Zero dependencies. Structural types only, so it also runs on Vercel Edge, Deno Deploy, or anything exposing waitUntil.

Install

npm install @upgoose/cloudflare

Use

Wrap your handler — errors are reported and re-thrown, so the runtime's own behaviour is unchanged:

import { wrapFetch } from "@upgoose/cloudflare";

export default {
  fetch: wrapFetch(
    (env) => ({
      dsn: env.UPGOOSE_DSN,
      environment: env.ENVIRONMENT ?? "production",
      release: env.BUILD_SHA,
    }),
    async (request, env, ctx) => {
      return new Response("hello");
    },
  ),
};

Or report by hand:

import { upgoose } from "@upgoose/cloudflare";

export default {
  async fetch(request, env, ctx) {
    const ug = upgoose({ dsn: env.UPGOOSE_DSN, request, ctx });
    try {
      return await handle(request, env);
    } catch (err) {
      ug.captureException(err, { route: "checkout" });
      return new Response("Internal Server Error", { status: 500 });
    }
  },
};

Why it isn't shaped like @upgoose/browser

The browser SDK is a singleton you init() once. That is correct in a tab and wrong in a Worker: one isolate serves many concurrent requests, so per-request state held at module level leaks between them — request A's URL attached to request B's error. Every client here is created per request and holds its own context.

Always pass ctx. Work started during a request is cancelled when the response returns unless it is handed to ctx.waitUntil(). Omitting it is the most common reason edge events go missing under load.

What gets captured

Message, stack, environment, release, plus request method, URL, CF colo, ray id and user agent.

Request headers are never sent. A Worker can read Authorization and Cookie; the browser SDK never could. Shipping them to a third party would leak session tokens, so they are not collected at all.

API

| Export | Purpose | | --- | --- | | wrapFetch(opts, handler) | Wrap a fetch handler. Reports and re-throws. | | upgoose(opts) | Create a per-request client. | | client.captureException(err, extra?) | Report an error. | | client.captureMessage(msg, level?, extra?) | Report a message. | | parseDsn(dsn) | Split a DSN into apiKey / apiUrl / projectId. |

beforeSend can transform or drop an event — return null to drop it.

Nothing in this SDK throws. A monitoring library that can break the request it monitors is worse than no monitoring.

Source maps

Upload with @upgoose/vite-plugin if you build with Vite, and keep release identical between the upload and this SDK or traces stay minified.

License

BSD-3-Clause