@belvador/react 0.1.0 → 0.3.0

package/README.md

@@ -35,7 +35,7 @@ Everything in `@belvador/browser` is exported here too.
 ## What it sends
 
 Errors only (exceptions, messages, breadcrumbs you turn on, attachments if you enable them).
-No tracing, session replay, logs or profiling — those items are dropped inside your app.
+No spans, session replay, logs, profiling or check-ins — those items are dropped inside your app.
 
 Before anything leaves your app the SDK removes `Authorization`, `Cookie` and `Set-Cookie`
 headers, request bodies and cookies, client IP headers, and masks credentials in URLs, query
@@ -48,6 +48,24 @@ each attempt times out after 10 s, failed sends retry at most 5 times, `429` rat
 respected, and a revoked key (`401`/`403`) stops sending for the life of the page or isolate.
 Every public function catches its own errors.
 
+## Link requests with one trace
+
+Off by default. `tracePropagation: { targets: [/^\/api\//, "https://api.example.com"] }` adds
+`traceparent` and `sentry-trace` headers to `fetch` calls to those URLs (relative patterns
+match same-origin paths), so a browser error and the server error behind the same request
+share one trace id. The receiving API must allow these headers in CORS. No spans or
+transactions are sent; `baggage` only with `baggage: true`. A View Transition the browser
+skipped on purpose is not reported unless you set `captureViewTransitionSkips: true`.
+See https://belvador.dev/docs/sdk/tracing
+
+## Check the connection
+
+"No errors" is not proof that errors arrive. Call `verifyIntegration()` from `@belvador/react` once after `init`:
+it sends one marked test error (never an issue), reads it back and resolves to
+`{ outcome: "verified" | "problem" | "unconfirmed", checks, docsUrl, … }`. It never throws.
+Requests the visitor cancelled (`AbortError`) are not reported unless you set `captureAborted: true`.
+See https://belvador.dev/docs/sdk/verify
+
 ## Status
 
 `0.x` — used by Belvador's own apps first. The API may still change before `1.0`.

package/dist/index.d.ts

@@ -1,9 +1,10 @@
 import type { ErrorBoundaryProps as EngineErrorBoundaryProps } from "@sentry/react";
 import { type ComponentType, type FC, type ReactElement } from "react";
-import type { BrowserOptions } from "@belvador/browser/internal";
+import { type BrowserOptions } from "@belvador/browser/internal";
+import type { VerificationResult, VerifyOptions } from "@belvador/core";
 export type ReactOptions = BrowserOptions;
 export type { FallbackRender } from "@sentry/react";
-export { SDK_VERSION, addBreadcrumb, captureException, captureMessage, close, flush, lastEventId, setContext, setTag, setTags, setUser, withScope, type BelvadorBreadcrumb, type BelvadorEvent, type BelvadorEventHint, type Scope, type SeverityLevel, } from "@belvador/core";
+export { SDK_VERSION, addBreadcrumb, captureException, captureMessage, close, flush, getDiagnostics, lastEventId, setContext, setTag, setTags, setUser, withScope, type BelvadorBreadcrumb, type BelvadorEvent, type BelvadorEventHint, type Diagnostic, type DiagnosticCode, type DiagnosticsSnapshot, type Scope, type SeverityLevel, type VerificationResult, type VerifyOptions, } from "@belvador/core";
 /**
  * Engine boundary props without the report dialog: it loads a script from
  * the DSN host, which Belvador never does (spec 01 §3).
@@ -23,3 +24,8 @@ export declare function reactErrorHandler(callback?: (error: unknown, errorInfo:
 }, eventId: string) => void): (error: unknown, errorInfo: {
     componentStack?: string;
 }) => void;
+/**
+ * Proves this app reports to Belvador from the browser: a captured and an uncaught
+ * verification error, read back from Belvador. Never automatic; always resolves.
+ */
+export declare function verifyIntegration(options?: VerifyOptions): Promise<VerificationResult>;

package/dist/index.js

@@ -3,8 +3,9 @@
 // privacy and sending rules. Importing this module does nothing until init().
 import { ErrorBoundary as EngineErrorBoundary, reactErrorHandler as engineReactErrorHandler, withErrorBoundary as engineWithErrorBoundary, } from "@sentry/react";
 import { createElement } from "react";
+import { verifyBrowser } from "@belvador/browser/internal";
 import { initReact } from "./internal.js";
-export { SDK_VERSION, addBreadcrumb, captureException, captureMessage, close, flush, lastEventId, setContext, setTag, setTags, setUser, withScope, } from "@belvador/core";
+export { SDK_VERSION, addBreadcrumb, captureException, captureMessage, close, flush, getDiagnostics, lastEventId, setContext, setTag, setTags, setUser, withScope, } from "@belvador/core";
 function withoutDialog(props) {
     const { showDialog: _show, dialogOptions: _dialog, ...rest } = props;
     return rest;
@@ -35,3 +36,10 @@ export function reactErrorHandler(callback) {
         }
     };
 }
+/**
+ * Proves this app reports to Belvador from the browser: a captured and an uncaught
+ * verification error, read back from Belvador. Never automatic; always resolves.
+ */
+export function verifyIntegration(options) {
+    return verifyBrowser(options);
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@belvador/react",
-  "version": "0.1.0",
+  "version": "0.3.0",
   "description": "Belvador error tracking for React 18/19: ErrorBoundary and root error handlers, errors only, private by default.",
   "license": "MIT",
   "author": "Belvador (https://belvador.dev)",
@@ -37,8 +37,8 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@belvador/browser": "0.1.0",
-    "@belvador/core": "0.1.0",
+    "@belvador/browser": "0.3.0",
+    "@belvador/core": "0.3.0",
     "@sentry/react": "10.76.2"
   },
   "publishConfig": {