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 --force to 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 :'( )
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 :'( )