🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.
TypeScript analyticsautogenevaluationlangchainlarge-language-modelsllama-indexllmllm-evaluationllm-observabilityllmopsmonitoringobservabilityopen-sourceopenaiplaygroundprompt-engineeringprompt-managementself-hostedycombinator
import { reportError } from "@/src/utils/reportError";
/**
* Turn a Web Worker `onerror` ErrorEvent into one legible, Sentry-reportable
* error.
*
* `Worker.onerror` fires when the worker *script* itself fails to load or throws
* during init — the dominant cause is a stale-deploy chunk 404. Handlers used to
* do `console.error("... Worker error:", event)` with the raw ErrorEvent; Sentry's
* captureConsoleIntegration stringifies that to "[object ErrorEvent]", discarding
* message/filename/lineno and making the resulting issues undiagnosable.
*
* This extracts the real fields and reports one proper Error with structured
* context through the {@link reportError} seam, which tags `area` and logs the
* companion line via `console.warn` (NOT `console.error`, so
* captureConsoleIntegration — which captures the "error" level — does not
* double-capture a second, opaque event for the same failure).
*
* It also CANCELS the event. Per the HTML spec an uncaught error inside a
* dedicated worker fires at the `Worker` object and, when that event is not
* canceled, is reported again on the owning document — where Sentry's
* `globalHandlers` integration captures it a second time, as an unhandled
* error, with none of the context below and a separate issue of its own.
* Cancelling is what "this error is handled" means, so it belongs in the one
* place that handles it rather than in each `onerror`, where it was missing
* from all of them.
*
* One implementation for every worker: each caller supplies its `area` tag, the
* `source` name the message should read as, and any extra context.
*/
export function reportWorkerLoadError({
area,
source,
event,
extra,
}: {
area: string;
/** What failed, as it should read in the message: a hook or worker name. */
source: string;
event: ErrorEvent;
extra?: Record<string, unknown>;
}): void {
event.preventDefault();
const details = `${event.message || "unknown"} @ ${event.filename || "?"}:${event.lineno ?? "?"}:${event.colno ?? "?"}`;
// Prefer the real Error when the worker threw during init; otherwise
// synthesize one from the ErrorEvent's fields so the message is legible.
const realError =
event.error instanceof Error
? event.error
: new Error(`[${source}] worker failed to load: ${details}`);
reportError(realError, {
area,
extra: {
...extra,
message: event.message,
filename: event.filename,
lineno: event.lineno,
colno: event.colno,
},
// Companion console line: carry source + location details exactly once in
// both branches — the pass-through Error's message lacks them, the
// synthesized one already embeds them. Console-only; the captured event is
// the Error above.
warnMessage: `${source} worker failed to load: ${details}`,
});
}