Error: Attempted import error: 'parseProviderOptions' is not exported from '@ai-sdk/provider-utils' (imported as 'parseProviderOptions').

[yamalight]

Description

When trying to deploy package to Vercel - build randomly throws following error:

../../node_modules/@ai-sdk/google/internal/dist/index.mjs
Attempted import error: 'parseProviderOptions' is not exported from '@ai-sdk/provider-utils' (imported as 'parseProviderOptions').
Import trace for requested module:
../../node_modules/@ai-sdk/google/internal/dist/index.mjs
../../node_modules/@ai-sdk/google-vertex/edge/dist/index.mjs
../../packages/astralcore/llm/config.ts
./app/admin/portal/books-qa/actions.ts
../../node_modules/@ai-sdk/google/internal/dist/index.mjs

Restarting the build usually fixes it.
This was not happening before.

Code example

No response

AI provider

@ai-sdk/google-vertex

Additional context

No response

[lgrammel]

This is most likely a installation issue due to dependencies.

What version of @ai-sdk/google-vertex are you on? What version of @ai-sdk/provider-utils is installed (indirectly)?

[yamalight]

We are using latest versions, here's the packages we install directly in package.json:

    "@ai-sdk/azure": "^1.2.5",
    "@ai-sdk/google": "^1.1.20",
    "@ai-sdk/google-vertex": "^2.1.29",
    "@ai-sdk/openai": "^1.2.5",
    "ai": "^4.1.61",

And @ai-sdk/provider-utils is using version 2.2.1.

The error does not seem to happen when building locally, and only sometimes crashes inside vercel deploys.

[lgrammel]

@ai-sdk/google-vertex uses @ai-sdk/google so this is where the issue might come in. Can you try moving to the latest versions and pinning them? provider-utils should not need a separate dependency.

Try these (current latest) versions:

  "@ai-sdk/azure": "1.3.2",
    "@ai-sdk/google": "1.2.2",
    "@ai-sdk/google-vertex": "2.2.2",
    "@ai-sdk/openai": "1.3.2",
    "ai": "4.2.2",

[JClackett]

This what I have installed:

 "@ai-sdk/openai": "1.3.3",
 "ai": "4.2.5",
 "openai": "4.89.0",

And now getting this when building on vercel

./node_modules/ai/dist/index.mjs
Attempted import error: 'createEventSourceParserStream' is not exported from '@ai-sdk/provider-utils' (imported as 'createEventSourceParserStream').

[lgrammel]

@JClackett can you check what version of the provider utils you have indirectly installed? do you have any other @ai-sdk packages installed?

[JClackett]

@lgrammel

provider in node_modules is "version": "2.2.1",

No other ai-sdk packages installed - assuming its to do with this commit

Does the ai package automatically get the new provider updates?

[lgrammel]

Also, @yamalight and @JClackett have you updated your package lockfiles?

[lgrammel]

@JClackett the provider utils version is correct - my current hypothesis is that the lockfile is outdated and might get in the way on vercel builds

[lgrammel]

@lgrammel

provider in node_modules is "version": "2.2.1",

No other ai-sdk packages installed - assuming its to do with this commit

Does the ai package automatically get the new provider updates?

double checking that you mean provider-utils (not provider which is a different pkg)

And yes, the packages update their dependencies and are pinned.

[JClackett]

@lgrammel Yeah provider-utils confirmed

[yamalight]

@lgrammel Lock file was updated and used 1.3.2 versions of google packages. I've just updated to new versions of all packages ai@4.2.5, *google*@1.3.3 and the problem so far did not resurface.

[JClackett]

Weird that this particular release is breaking stuff though, was just a regular dep bot update updating the ai package, looking at my builds - I didnt do anything

[yamalight]

@lgrammel FYI: it still happens for us even with latest versions. simply restarting failed builds does fix it as before.

[lgrammel]

So both createEventSourceParserStream and parseProviderOptions were functionality introduced into @ai-sdk/provider-utils at specific versions. When they were introduced, dependent libraries (such as the providers and the ai library) were automatically updated to use exactly the latest version, per changesets. This is verified by our CI and I manually double checked the versions.

Therefore the issue is most likely an installation issue. Three potential problem sources come to mind:

• outdated lockfiles (ruled out)
• caching in CI (is there a way to clean the cache?)
• other libraries that require older versions of @ai-sdk/provider-utils (very unlikely, the newer version should also be installed)

Do you use build caching in CI? is there a way to reset the cache?