-
Notifications
You must be signed in to change notification settings - Fork 74
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
Switch openai
to openai-edge
#66
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
openai
to openai-edge
openai
to openai-edge
@@ -125,6 +125,7 @@ | |||
"react": "^16.8.0 || ^17.0.0 || ^18.0.0" | |||
}, | |||
"dependencies": { | |||
"@nick.heiner/openai-edge": "1.0.1-7", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did we need to fork openai-edge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops – I thought I'd left a note about this somewhere: dan-kwiat/openai-edge#6.
Axios doesn't appear to support streaming in the browser, and since we want AI.JSX to be able to run in browser, that's a no-go for us.
Loom showing streaming in the browser
We still don't stream the UI demos (e.g. recipe builder) because filling in UI pieces bit-by-bit could be worse than buffering.
The other approach would have been to do something like langchain/src/util/axios-fetch-adapter.js..