Filter out browser extension errors from error handler

Explicitly detect and filter errors originating from browser extensions
by checking for extension URL schemes (chrome-extension://,
moz-extension://, safari-extension://, safari-web-extension://) in the
error's filename and stack trace. This prevents unrelated extension
errors from being shown to users.

Co-Authored-By: Claude (Opus 4.6) <noreply@anthropic.com>

Author: silverwind

web_src/js/modules/errors.ts

@@ -38,6 +38,11 @@ export function processWindowErrorEvent({error, reason, message, type, filename,
     if (runModeIsProd) return;
   }
 
+  // Filter out errors from browser extensions. Extension scripts use these URL schemes which
+  // can appear in `filename` or the error's stack trace.
+  const extensionPattern = /(chrome|moz|safari(-web)?)-extension:\/\//;
+  if (extensionPattern.test(filename ?? '') || extensionPattern.test(err?.stack ?? '')) return;
+
   // If the error stack trace does not include the base URL of our script assets, it likely came
   // from a browser extension or inline script. Do not show such errors in production.
   if (err instanceof Error && !err.stack?.includes(assetBaseUrl) && runModeIsProd) return;