Improve Sentry Error Filtering (#772)

* fix: miniflare from errors from users should be ignored by Sentry

.changeset/breezy-steaks-visit.md

@@ -0,0 +1,8 @@
+---
+"wrangler": patch
+---
+
+fix: We want to prevent any user created code from sending Events to Sentry,
+which can be captured by `uncaughtExceptionMonitor` listener.
+Miniflare code can run user code on the same process as Wrangler,
+so we want to return `null` if `@miniflare` is present in the Event frames.

packages/wrangler/src/reporting.ts

@@ -30,6 +30,21 @@ export function initReporting() {
       // from their worker during development
       return null;
     },
+    /**
+     * We want to prevent any user created code from sending Events to Sentry,
+     * which can be captured by "uncaughtExceptionMonitor" listener.
+     * Miniflare code runs on the same process as Wrangler, so we want to return `null`
+     * if "@miniflare" is present in the Event frames.
+     */
+    beforeSend: (event) => {
+      return !event.exception?.values?.some((value) =>
+        value.stacktrace?.frames?.some((frame) =>
+          frame.module?.includes("@miniflare")
+        )
+      )
+        ? event
+        : null;
+    },
     dsn: "https://5089b76bf8a64a9c949bf5c2b5e8003c@o51786.ingest.sentry.io/6190959",
     tracesSampleRate: 1.0,
     integrations: [