fix(deps): relax peer dependency version rules #33
Conversation
This file contains 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.
As discussed on Slack, I wonder if it is legitimate to caret-pin exact versions of the peer dependencies.
This leads to an uncomfortable situation if a peer package has released a new version since the last cut of the TS SDK. For example the latest version of the Vercel AI SDK is 0.0.24 , but the TS SDK had it pinned at 0.0.9. This is solved in v0.0.507 of the SDK but in the meantime it produced NPM errors which are hard to solve : either the user had to downgrade the AI SDK they used, or to
npm install --forceto ignore the error.IMO it is much more flexible to allow peer dependencies at a known version or above. WDYT ?
(btw since i noticed this, AI SDK is now at 0.0.31 so we are back to being incompatible :'( )