-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First class support for @azure/openai library #618
Comments
@cahaseler Why is it not recommended? Under the hood Azure just uses OpenAI API? I do agree the convergence is annoying and handling content filters with Vercel's AI SDK is not on par with Azure's SDK and not yet currently supported. |
All I have is the quote above from the openai-node devs encouraging people to use the MS provided one. They didn't go into exactly what bugs, I just tend to listen to package devs when they tell me I'm going to get into "subtle type inconsistency" bug territory. I'm using the node package without issue right now, but I won't say I'm not nervous about it. |
I am using this function instead of the available one.
|
Requirest for the Maintainers - please consider supporting Azure OpenAI as first class citizen. Anyone who wants to seriously use GPT-3 or -4 for production purposes does it in Azure, as it is way more reliable than openai.com, to the level, that I would consider openai.com not fit for production purposes. Anytime they announce a new feature their system gets "DDOS"-ed :) |
Was able to make it work with the Steps:
|
Feature Description
openai-node documents specifically call out the Azure OpenAI api as having subtly different behaviors compared to the OpenAI api, and recommend using the @azure/openai library instead. See: https://github.com/openai/openai-node#azure-openai
The @azure/openai SDK returns an
AsyncIterable<ChatCompletions>
object, which can't be used to create an OpenAIStream.Here's how I use it:
Use Case
White technically you can use the openai package, it's not recommended and given that the APIs are likely to continue to diverge I'd rather not be troubleshooting the difficult kind of bugs this is likely to introduce.
Additional context
No response
The text was updated successfully, but these errors were encountered: