raindrop-ai 0.2.1 → 0.2.2

package/dist/index.mjs

@@ -3,6 +3,7 @@ import {
   MAX_RETRY_DELAY_MS,
   POST_SHUTDOWN_TIMEOUT_MS,
   SHUTDOWN_DEADLINE_MS,
+  authHintForKey,
   capText,
   mirrorPartialEventToLocalDebugger,
   normalizeFeatureFlags,
@@ -17,8 +18,9 @@ import {
   runWithTracingSuppressed,
   setDefaultMaxTextFieldChars,
   stringifyBounded,
-  tracing
-} from "./chunk-UTCK3OAC.mjs";
+  tracing,
+  withRoutingContext
+} from "./chunk-2EGS66V2.mjs";
 import {
   __commonJS,
   __toESM
@@ -10155,6 +10157,7 @@ var Raindrop = class {
     setDefaultMaxTextFieldChars(config.maxTextFieldChars);
     this.maxTextFieldChars = resolveMaxTextFieldChars(config.maxTextFieldChars);
     this.writeKey = (_a = config.writeKey) != null ? _a : "";
+    this.authHint = authHintForKey(this.writeKey);
     this.localDebuggerUrlOpt = config.localWorkshopUrl === false ? null : config.localWorkshopUrl;
     this.awaitSpanFlushOpt = config.awaitSpanFlush;
     this.apiUrl = (_b = this.formatEndpoint(config.endpoint)) != null ? _b : `https://api.raindrop.ai/v1/`;
@@ -10217,6 +10220,14 @@ var Raindrop = class {
   /**
    * Begins a new interaction.
    *
+   * The interaction's routing binding lives until `finish()` (which unbinds it
+   * by identity, so it is removed even if `finish()` runs inside a nested
+   * `withSpan`/`withTool`/`asCurrent` scope or a detached task). One exception:
+   * calling `begin()` INSIDE an `asCurrent(fn)` scope pushes the binding within
+   * that scope, so it dies when the scope exits (matching the Python SDK's
+   * token-reset semantics) — start such interactions outside `asCurrent`, or
+   * keep their work inside the same scope.
+   *
    * @param traceContext - The trace context for the interaction.
    * @returns The interaction object.
    */
@@ -10234,6 +10245,22 @@ var Raindrop = class {
   tracer(globalProperties) {
     return this._tracing.tracer(globalProperties);
   }
+  /**
+   * Scope all spans created inside `fn` (and its awaited continuations) to this
+   * client's project/key, without an interaction. Use it around auto-
+   * instrumented calls (an LLM SDK call, a framework invocation) that aren't
+   * wrapped by `begin()`/`finish()` so their spans route to this client's
+   * project in a multi-client process. The binding lasts exactly the duration
+   * of `fn` — it is removed when `fn` returns or throws.
+   *
+   * @example
+   * ```ts
+   * const answer = await raindrop.asCurrent(() => llm.chat({ ... }));
+   * ```
+   */
+  asCurrent(fn) {
+    return withRoutingContext({ projectId: this.projectId, authHint: this.authHint }, fn);
+  }
   createSpanProcessor(processorOptions) {
     return this._tracing.createSpanProcessor(processorOptions);
   }

package/dist/tracing/index.d.mts

@@ -1,9 +1,24 @@
+import { Raindrop, RaindropSpanProcessor, PartialAiTrackEvent, Interaction, Tracer } from '../index.mjs';
 import { Instrumentation } from '@opentelemetry/instrumentation';
 import * as traceloop from '@traceloop/node-server-sdk';
-import { Raindrop, RaindropSpanProcessor, PartialAiTrackEvent, Interaction, Tracer } from '../index.mjs';
 import '@opentelemetry/api';
 import 'zod';
 
+/**
+ * Tracing core - the real tracing implementation.
+ *
+ * Two modes:
+ *
+ * 1. DEFAULT: Raindrop manages everything
+ *    - Creates NodeSDK, registers instrumentations, exports traces
+ *    - Customer just uses raindrop.begin(), withSpan(), etc.
+ *
+ * 2. EXTERNAL OTEL (useExternalOtel: true): Customer has their own NodeSDK
+ *    - Raindrop does NOT create a NodeSDK (would conflict!)
+ *    - Customer adds raindrop.createSpanProcessor() to their NodeSDK
+ *    - Customer calls raindrop.getInstrumentations() to get configured instrumentations
+ */
+
 interface TracingOptions extends traceloop.InitializeOptions {
     /**
      * Set to true when you have your own OpenTelemetry NodeSDK.

package/dist/tracing/index.d.ts

@@ -1,9 +1,24 @@
+import { Raindrop, RaindropSpanProcessor, PartialAiTrackEvent, Interaction, Tracer } from '../index.js';
 import { Instrumentation } from '@opentelemetry/instrumentation';
 import * as traceloop from '@traceloop/node-server-sdk';
-import { Raindrop, RaindropSpanProcessor, PartialAiTrackEvent, Interaction, Tracer } from '../index.js';
 import '@opentelemetry/api';
 import 'zod';
 
+/**
+ * Tracing core - the real tracing implementation.
+ *
+ * Two modes:
+ *
+ * 1. DEFAULT: Raindrop manages everything
+ *    - Creates NodeSDK, registers instrumentations, exports traces
+ *    - Customer just uses raindrop.begin(), withSpan(), etc.
+ *
+ * 2. EXTERNAL OTEL (useExternalOtel: true): Customer has their own NodeSDK
+ *    - Raindrop does NOT create a NodeSDK (would conflict!)
+ *    - Customer adds raindrop.createSpanProcessor() to their NodeSDK
+ *    - Customer calls raindrop.getInstrumentations() to get configured instrumentations
+ */
+
 interface TracingOptions extends traceloop.InitializeOptions {
     /**
      * Set to true when you have your own OpenTelemetry NodeSDK.