@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/cloudflareUse
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
