reproduction: customProvider loses video models from v3 fallback providers - #21113
Draft
ai-sdk-factory[bot] wants to merge 1 commit into
Draft
ai-sdk-factory[bot] wants to merge 1 commit into
ai-sdk-factory[bot] wants to merge 1 commit into
Conversation
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug
customProvider loses video models from v3 fallback providers
Reproduction
ai@7.0.106,@ai-sdk/fal@2.0.58, andzod@4.4.3reproduced the issue: direct lookup returned v3, alias and registry lookups returned v4, but custom-provider fallback threwAI_NoSuchModelError.packages/ai/src/model/as-provider-v4.tsomits the experimentalvideoModelmethod when adapting ProviderV3, whilepackages/ai/src/registry/custom-provider.tsattempts video fallback lookup on that adapted provider.@ai-sdk/fal@3.0.45avoids the failure, but ProviderV3 remains an explicitly accepted fallback type, so the older provider behavior is supported rather than invalid.examples/ai-functions/src/reproduction/custom-provider-v3-video-fallback.tsconfirms direct, alias, and registry lookup succeed, then fails because fallback lookup does not return the v3 video model adapted to v4.Relevant Documentation
Related Issues
Reproduces #21110