-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Type error to do with BaseLanguageModel and CallOptions #3793
Comments
🤖 It's great to see that you've identified an issue and are looking to contribute to langchainjs! Your effort is much appreciated. I encourage you to go ahead and create a pull request with your proposed solution to address this type error. The maintainers will review your PR and determine if the change should be merged. Keep up the good work! This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
I'm having the same issue, can't use latest version. any workaround besides of using 0.0.203? |
Workaround: Add
|
having same problem, using workaround. FYI @jacoblee93 something strange going on here... |
Thanks for the heads up and sorry for missing this - the workaround is good but is there a code example/ If you have multiple packages installed do the instructions here fix it? https://js.langchain.com/docs/get_started/installation#installing-integration-packages |
@mieslep perhaps? |
I've had no luck following the linked instructions. Here's what you can use to reproduce the errors: package.json
main.ts
|
And it doesn't look like you have Edit: Never mind, I am able to repro with I see:
|
I think #3953 fixes this! Can you try locking your core version to I was occasionally able to repro another typing bug caused by a polyfill overriding a global stream in that OpenAI's SDK uses. Please reopen another issue if you see this. |
Introduced here I believe: #3709
0.0.203 is a working version.
Stack trace:
The text was updated successfully, but these errors were encountered: