Bump ai dependency to v4?

[tmcw]

Hi! We use both this module as well as the vercel ai module directly in our application. This module pins ai at 4, which means that if we upgraded to 4 in our application, we'd still have a v3 version of ai sticking around as a transitive dependency. Could this module bump its dependency on ai?

[ankrgyl]

CC @ibolmo

[ibolmo]

Thanks for reporting this @tmcw. We're currently deciding whether to keep the ai-sdk integration as part of the SDK (perhaps move to an optional peer dependency) or if we'll have a separate package i.e. @braintrust/ai-sdk

In either case, we'll have to consider backward compatibility requirements to not affect current users. Curious on your take, though, if you'd have a preference.

[tmcw]

Moving them to a peer dependency would be ideal, I think - we don't use the integrations and they seem like they could be a constantly-expanding part of the API surface, if you want to support anthropic's, for example, as well. Also it kind of looks like (didn't thoroughly read through) the ai import was only used for types.