Version issues with @langchain/core and multiple providers using deno #7688
Replies: 2 comments
-
A similar issue has been reported regarding type mismatch errors in Deno when using different versions of In your case, you might want to ensure that all your imports, especially for To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report |
Beta Was this translation helpful? Give feedback.
-
In my case, I'm defining the inputs in my deno.jsonc file (included). And it should be using this when importing in my code. It should be using whatever version is defined in my deno.jsonc file so there shouldn't be a version mismatch at all. |
Beta Was this translation helpful? Give feedback.
-
Checked other resources
Commit to Help
Example Code
Description
I'm having a lot of trouble to get multiple providers to work together with the same versions of langchain core and lanchain community.
Often, I get the problem:
Right now, by using the latest langchain/community (0.3.30) and latest langchain/core (0.3.40) I'm able to get OpenAI, Bedrock, Anthropic, Gemini & VertexAI working.
However, XAI & Groq both have this issue (e.g. this is for groq):
Normally I think the answer is in package.json you can force specific versions. But I'm using deno which doesn't seem to have this feature.
Frustratingly it's only these two providers which have this problem, is there a workaround here?
Maybe I should request that these get updated to latest langchain core?
System Info
deno 2.1.9+d29f9f9
Beta Was this translation helpful? Give feedback.
All reactions