Don't swallow fetch TypeError as CORS in non-browser environments (#1595)
Co-authored-by: Felix Weinberger <3823880+felixweinberger@users.noreply.github.com> Co-authored-by: Felix Weinberger <fweinberger@anthropic.com>
This commit is contained in:
parent
f9fda807d3
commit
13a0d345c0
1 changed files with 161 additions and 20 deletions
9
.changeset/tame-camels-greet.md
Normal file
9
.changeset/tame-camels-greet.md
Normal file
|
|
@ -0,0 +1,9 @@
|
|||
---
|
||||
'@modelcontextprotocol/client': patch
|
||||
---
|
||||
|
||||
Don't swallow fetch `TypeError` as CORS in non-browser environments. Network errors
|
||||
(DNS resolution failure, connection refused, invalid URL) in Node.js and Cloudflare
|
||||
Workers now propagate from OAuth discovery instead of being silently misattributed
|
||||
to CORS and returning `undefined`. This surfaces the real error to callers rather
|
||||
than masking it as "metadata not found."
|
||||
Loading…
Reference in a new issue