typescript changedcli-sdks-libraries/sdks/typescript
Nearest release: v2.1.300, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−5removed
From line
88
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 88, old and new numbered
/
from line 88
8888
8989## Streaming responses
9090
91The SDK provides support for streaming responses using Server Sent Events (SSE).
91The SDK provides support for streaming responses using Server-Sent Events (SSE).
9292
9393```typescript
9494const client = new Anthropic();
from line 275
275275
276276### MCP error handling
277277
278The conversion functions throw `UnsupportedMCPValueError` if an MCP value isn't supported by the Claude API (for example, unsupported content type, unsupported MIME type, non-http/https resource link).
278The conversion functions throw `UnsupportedMCPValueError` if an MCP value isn't supported by the Claude API (for example, unsupported content type, unsupported MIME type, non-HTTP/HTTPS resource link).
279279
280280## Message batches
281281
from line 330
330330* an `fs.ReadStream`
331331* the return value of the `toFile` helper
332332
333Set the content-type explicitly as the files API will not infer it for you:
333Set the content type explicitly as the Files API will not infer it for you:
334334
335335```typescript
336336import fs from "node:fs";
from line 745
745745## Runtime support
746746
747747<Accordion title="Browser usage">
748 Enabling the `dangerouslyAllowBrowser` option can be dangerous because it exposes your secret API credentials in the client-side code. Web browsers are inherently less secure than server environments, any user with access to the browser can potentially inspect, extract, and misuse these credentials. This could lead to unauthorized access using your credentials and potentially compromise sensitive data or functionality.
748 Enabling the `dangerouslyAllowBrowser` option can be dangerous because it exposes your secret API credentials in the client-side code. Web browsers are inherently less secure than server environments. Any user with access to the browser can potentially inspect, extract, and misuse these credentials. This could lead to unauthorized access using your credentials and potentially compromise sensitive data or functionality.
749749
750750 **When might this not be dangerous?**
751751
from line 784
7847842. Changes to library internals which are technically public but not intended or documented for external use.
7857853. Changes that aren't expected to impact the vast majority of users in practice.
786786
787Backward-compatibility is taken seriously to ensure you can rely on a smooth upgrade experience.
787Backward compatibility is taken seriously to ensure you can rely on a smooth upgrade experience.
788788
789789## Frequently asked questions
790790
No line in this hunk matches that.