@defjs/opentelemetry-server 0.0.2 → 0.0.3

package/README.md

@@ -10,7 +10,7 @@ It is a middleware plugin — the plugin form of an interceptor chain. Your appl
 bun add @defjs/core @defjs/opentelemetry-server @opentelemetry/api @opentelemetry/core
 ```
 
-The package is ESM and requires `@defjs/core` as a peer in the `^0.5.0` range.
+The package is ESM and requires `@defjs/core` as a peer in the `^0.6.0` range.
 
 ## Quick start
 

package/index.d.ts

@@ -39,7 +39,7 @@ interface OpenTelemetryServerTransportOptions<TResponse> {
  *
  * - The HTTP span ends as soon as `responseHook` returns; the hook is not awaited, so only its synchronous part can still change the span. A status of 400 or above ends it `ERROR` with `error.type` set to the status string; 100–399 leaves its status unset. An asynchronous hook rejection after end is reported through `diag.error`; configure `diag.setLogger(...)` from `@opentelemetry/api` to receive it. It cannot append events to an ended span.
  *
- * - A rejection through the interceptor has no response status and does not call `responseHook`. That includes a network failure, caller cancellation, an abort whose reason is `TimeoutError`, any declared-body read failure (`BodyFailure`, including text, blob, and bytes, not only JSON), and a progress observer failure (`EXT_OBSERVER_FAILED`). The span ends `ERROR` with `error.type` set to the thrown class name, such as `TypeError`, `Error` or `BodyFailure`. Caller cancellation is `Error` whatever the abort reason. There is no `timeout` option; a deadline is `abort`.
+ * - A rejection through the interceptor has no response status and does not call `responseHook`. That includes a network failure, caller cancellation, an abort whose reason is `TimeoutError`, any declared-body read failure (`BodyFailure`, including text, blob, and bytes, not only JSON), and a progress observer failure (`EXT_OBSERVER_FAILED`). The span ends `ERROR` with `error.type` set to the thrown class name, such as `TypeError`, `Error` or `BodyFailure`. Caller cancellation is `Error` whatever the abort reason. There is no `timeout` option; a deadline is `signal`.
  *
  * Pass `{ enabled: false }` to skip HTTP instrumentation. Span hooks run only when a `tracer` is supplied.
  *

package/index.js

@@ -272,12 +272,12 @@ const CLIENT_EXCEPTIONS = {
 /**
 * Caller cancellation produces no log. An abort whose reason is `TimeoutError` or `ERR_TIMEOUT` still logs.
 *
-* `request.abort` alone is not cancellation: WebSocket `finish()` aborts that same signal
+* `request.signal` alone is not cancellation: WebSocket `finish()` aborts that same signal
 * when a connect fails. Cancellation is an abort sentinel from any `@defjs/core` copy, or an
-* `AbortError`, on the rejection or on `request.abort.reason`. There is no `timeout` option.
+* `AbortError`, on the rejection or on `request.signal.reason`. There is no `timeout` option.
 */
 function isCallerCancellation(request, error) {
-	const reason = request.abort?.reason;
+	const reason = request.signal?.reason;
 	if (isTimeoutCause(error) || isTimeoutCause(reason)) return false;
 	return isAbortCause(error) || isAbortCause(reason);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@defjs/opentelemetry-server",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "Append OpenTelemetry interceptors to an application-owned Defjs client.",
   "bugs": {
     "url": "https://github.com/defjs/defjs/issues"
@@ -17,7 +17,7 @@
     "@opentelemetry/api-logs": "^0.223.0"
   },
   "peerDependencies": {
-    "@defjs/core": "^0.5.0",
+    "@defjs/core": "^0.6.0",
     "@opentelemetry/api": "^1.0.0",
     "@opentelemetry/core": "^2.0.0 || ^3.0.0"
   },