@raindrop-ai/ai-sdk 0.0.19-beta.3 → 0.0.19

package/README.md

@@ -58,7 +58,20 @@ If `userId` is missing from both `wrap()` context and `eventMetadata()`, the SDK
 
 ## Runtime support
 
-### Node.js (recommended)
+### Browsers and edge runtimes
+
+Use the browser entrypoint:
+
+```ts
+import { createRaindropAISDK } from "@raindrop-ai/ai-sdk/browser";
+```
+
+The SDK works without `async_hooks` shims. When `AsyncLocalStorage` is not available,
+Raindrop falls back to synchronous context scoping: nested work in the same call stack
+still inherits context, but automatic propagation across arbitrary async boundaries is
+not guaranteed.
+
+### Node.js
 
 Use the default import:
 
@@ -66,17 +79,23 @@ Use the default import:
 import { createRaindropAISDK } from "@raindrop-ai/ai-sdk";
 ```
 
+In Node, the default entrypoint wires up `AsyncLocalStorage` automatically.
+
 ### Cloudflare Workers
 
 Cloudflare Workers can provide `AsyncLocalStorage` via `node:async_hooks` when `nodejs_compat` is enabled ([docs](https://developers.cloudflare.com/workers/runtime-apis/nodejs/asynclocalstorage/)).
 
-Use the Workers entrypoint:
+If `nodejs_compat` is enabled, use the Workers entrypoint:
 
 ```ts
 import { createRaindropAISDK } from "@raindrop-ai/ai-sdk/workers";
 ```
 
-If `nodejs_compat` is not enabled, AsyncLocalStorage-based context propagation cannot work.
+This enables real `AsyncLocalStorage` propagation in Workers.
+
+If `nodejs_compat` is not enabled, use the browser entrypoint instead. The SDK still works,
+but it uses the same synchronous fallback described above rather than real
+`AsyncLocalStorage`.
 
 ## Supported AI SDK Versions