Bumping to SDK v1.13.2 (#17)

* fix(use-mcp): connect to mcp fails with handleMessage function

* Upping the SDK version cooks every test

* checking out neighbouring SDK

* Getting more random port collisions locally :/

I will fix this properly... eventually.

* Running `wrangler types` on example servers

* Updated to SDK v1.13.2

* prettier

---------

Co-authored-by: ksankaran <kv.coder@gmail.com>
Co-authored-by: Glen Maddern <glen@glenmaddern.com>
This commit is contained in:
Glen Maddern 2025-07-02 10:42:47 +10:00 • committed by GitHub
commit f770d57e0a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -235,7 +235,7 @@ export function useMcp(options: UseMcpOptions): UseMcpResult {
// Use stable addLog
addLog('debug', `[Transport] Received: ${JSON.stringify(message)}`)
// @ts-ignore
clientRef.current?.handleMessage(message) // Forward to current client
clientRef.current?.handleMessage?.(message) // Forward to current client
}
transportInstance.onerror = (err: Error) => {
// Transport errors usually mean connection is lost/failed definitively for this transport