glitchgrab 1.23.1 → 1.25.0

package/README.md

@@ -454,6 +454,37 @@ import { GlitchgrabErrorBoundary } from "glitchgrab";
 | `onError` | `(error: Error) => void` | - | Called on unhandled errors |
 | `onReportSent` | `(result: ReportResult) => void` | - | Called after a report is sent |
 | `fallback` | `ReactNode` | - | Error boundary fallback UI |
+| `ignoreErrors` | `(string \| RegExp)[]` | - | Skip auto-capture for errors whose message matches (substring for `string`, `.test()` for `RegExp`) |
+
+### Ignoring known-noisy errors
+
+Some errors that reach `window.onerror` aren't app bugs — browser extension bridges (Grammarly, password managers, etc.) can throw errors that look like they come from your page. If you keep seeing the same non-actionable signature auto-filed as a report, suppress it:
+
+```tsx
+<GlitchgrabProvider
+  token={process.env.NEXT_PUBLIC_GLITCHGRAB_TOKEN!}
+  ignoreErrors={[/Object Not Found Matching Id.*MethodName:update/]}
+>
+  {children}
+</GlitchgrabProvider>
+```
+
+## Do I need a Content-Security-Policy allowance?
+
+If your app sets a CSP header (e.g. via `proxy.ts` / `middleware.ts` in Next.js), allow Glitchgrab's API host so `fetch` calls from the SDK aren't blocked:
+
+```ts
+// proxy.ts / middleware.ts
+response.headers.set(
+  "Content-Security-Policy",
+  "connect-src 'self' https://glitchgrab.dev; ..." // plus your existing directives
+);
+```
+
+- `connect-src https://glitchgrab.dev` — required for `sendReport`, `enhanceText`, `transcribeAudio`, and the report-fetching hooks/REST calls. All SDK requests go to this single host by default.
+- If you pass a custom `baseUrl` prop, allow that host instead (self-hosted or proxied deployments).
+- Screenshot capture (`html2canvas-pro`) runs entirely client-side against `document.body` — no network request, no extra `img-src`/`connect-src` needed for it.
+- No `script-src`, `style-src`, or `frame-src` allowances are required — the SDK doesn't load remote scripts, styles, or iframes.
 
 ## How does auto-capture work?
 

package/dist/index.d.mts

@@ -12,6 +12,12 @@ interface GlitchgrabConfig {
     breadcrumbs?: boolean;
     /** Max breadcrumbs to keep (default: 50) */
     maxBreadcrumbs?: number;
+    /**
+     * Skip auto-capture for errors matching any of these patterns (checked against the
+     * error message). String = substring match, RegExp = `.test()`. Use for known-noisy
+     * signatures that aren't app bugs — e.g. browser extension bridge errors.
+     */
+    ignoreErrors?: (string | RegExp)[];
 }
 type ReportType = "BUG" | "FEATURE_REQUEST" | "QUESTION" | "OTHER";
 type ReportSeverity = "low" | "medium" | "high";
@@ -91,6 +97,12 @@ interface GlitchgrabProviderProps {
     types?: ReportType[];
     /** Show severity picker for BUG type (default: true) */
     showSeverity?: boolean;
+    /**
+     * Skip auto-capture for errors matching any of these patterns (checked against the
+     * error message). String = substring match, RegExp = `.test()`. Use for known-noisy
+     * signatures that aren't app bugs — e.g. browser extension bridge errors.
+     */
+    ignoreErrors?: (string | RegExp)[];
 }
 interface ReportButtonProps {
     position?: "bottom-right" | "bottom-left" | "top-right" | "top-left";

package/dist/index.d.ts

@@ -12,6 +12,12 @@ interface GlitchgrabConfig {
     breadcrumbs?: boolean;
     /** Max breadcrumbs to keep (default: 50) */
     maxBreadcrumbs?: number;
+    /**
+     * Skip auto-capture for errors matching any of these patterns (checked against the
+     * error message). String = substring match, RegExp = `.test()`. Use for known-noisy
+     * signatures that aren't app bugs — e.g. browser extension bridge errors.
+     */
+    ignoreErrors?: (string | RegExp)[];
 }
 type ReportType = "BUG" | "FEATURE_REQUEST" | "QUESTION" | "OTHER";
 type ReportSeverity = "low" | "medium" | "high";
@@ -91,6 +97,12 @@ interface GlitchgrabProviderProps {
     types?: ReportType[];
     /** Show severity picker for BUG type (default: true) */
     showSeverity?: boolean;
+    /**
+     * Skip auto-capture for errors matching any of these patterns (checked against the
+     * error message). String = substring match, RegExp = `.test()`. Use for known-noisy
+     * signatures that aren't app bugs — e.g. browser extension bridge errors.
+     */
+    ignoreErrors?: (string | RegExp)[];
 }
 interface ReportButtonProps {
     position?: "bottom-right" | "bottom-left" | "top-right" | "top-left";