failed fetches not mapped to APICallError

[YousefED]

Description

According to this code, the intention seems to map failed fetches to APICallError.

However, the error detection is looking for fetch failed, while browser-based fetch() errors normally throw Failed to Fetch,

It could be that in nodejs / next environments fetch failed is thrown, but I think we should handle both cases?

AI SDK Version

No response

[lgrammel]

can you describe the bug that you have encountered, i.e. what is the impact of the above? from which ai sdk version and file is the above code?

[YousefED]

Source:

• ai/packages/provider-utils/src/post-to-api.ts

  Line 162 in 05c2da5

  if (error instanceof TypeError && error.message === 'fetch failed') {

• ai/packages/provider-utils/src/get-from-api.ts

  Line 92 in 05c2da5

  if (error instanceof TypeError && error.message === 'fetch failed') {

version: latest, 4.3.16

Impact: I want to develop code (for a library) that handles errors caused by network errors / API availability different from errors caused by processing LLM responses. For this, I check if caught errors are an instance of APICallError. With the current bug, I'm unable to do so.