@belvador/react 0.2.0 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +11 -1
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -35,7 +35,7 @@ Everything in `@belvador/browser` is exported here too.
35
35
  ## What it sends
36
36
 
37
37
  Errors only (exceptions, messages, breadcrumbs you turn on, attachments if you enable them).
38
- No tracing, session replay, logs or profiling — those items are dropped inside your app.
38
+ No spans, session replay, logs, profiling or check-ins — those items are dropped inside your app.
39
39
 
40
40
  Before anything leaves your app the SDK removes `Authorization`, `Cookie` and `Set-Cookie`
41
41
  headers, request bodies and cookies, client IP headers, and masks credentials in URLs, query
@@ -48,6 +48,16 @@ each attempt times out after 10 s, failed sends retry at most 5 times, `429` rat
48
48
  respected, and a revoked key (`401`/`403`) stops sending for the life of the page or isolate.
49
49
  Every public function catches its own errors.
50
50
 
51
+ ## Link requests with one trace
52
+
53
+ Off by default. `tracePropagation: { targets: [/^\/api\//, "https://api.example.com"] }` adds
54
+ `traceparent` and `sentry-trace` headers to `fetch` calls to those URLs (relative patterns
55
+ match same-origin paths), so a browser error and the server error behind the same request
56
+ share one trace id. The receiving API must allow these headers in CORS. No spans or
57
+ transactions are sent; `baggage` only with `baggage: true`. A View Transition the browser
58
+ skipped on purpose is not reported unless you set `captureViewTransitionSkips: true`.
59
+ See https://belvador.dev/docs/sdk/tracing
60
+
51
61
  ## Check the connection
52
62
 
53
63
  "No errors" is not proof that errors arrive. Call `verifyIntegration()` from `@belvador/react` once after `init`:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@belvador/react",
3
- "version": "0.2.0",
3
+ "version": "0.4.0",
4
4
  "description": "Belvador error tracking for React 18/19: ErrorBoundary and root error handlers, errors only, private by default.",
5
5
  "license": "MIT",
6
6
  "author": "Belvador (https://belvador.dev)",
@@ -37,8 +37,8 @@
37
37
  "node": ">=18"
38
38
  },
39
39
  "dependencies": {
40
- "@belvador/browser": "0.2.0",
41
- "@belvador/core": "0.2.0",
40
+ "@belvador/browser": "0.4.0",
41
+ "@belvador/core": "0.4.0",
42
42
  "@sentry/react": "10.76.2"
43
43
  },
44
44
  "publishConfig": {