fix: move AI SDK packages to peer dependencies #722
Merged
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.
Summary
aiand@ai-sdk/openaifrom direct dependencies to peer dependencies@ai-sdk/reactas optional peer dependency (was previously undeclared despite being imported)Problem
Currently,
aiand@ai-sdk/openaiare pinned as direct dependencies ("ai": "5.0.103"). This causes issues for consumers using different AI SDK versions (e.g., AI SDK 6):AIChatAgentAdditionally,
@ai-sdk/reactis imported inai-react.tsxbut was never declared in package.json, relying on consumers having it installed transitively.Solution
ai: required peer dep (>=5.0.0) - core AI SDK types and functions@ai-sdk/openai: optional peer dep (>=2.0.0) - only needed for codemode feature@ai-sdk/react: optional peer dep (>=1.0.0) - only needed for React hooksAll three packages are also added to
devDependenciesfor local development and testing.Breaking Changes
Consumers who don't already have
aiinstalled will need to add it explicitly. In practice, anyone using the AI features is already installingaiseparately anyway.Closes #42
🤖 Generated with Claude Code