Google GenAI Library Deprecated

[Steffen911]

Checked other resources

• This is a bug, not a usage question. For questions, please use the LangChain Forum (https://forum.langchain.com/).
• I added a very descriptive title to this issue.
• I searched the LangChain.js documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.
• I am sure that this is a bug in LangChain.js rather than my code.
• The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code

We're using @langchain/google-genai in our code. This references https://www.npmjs.com/package/@google/generative-ai which links to https://github.com/google-gemini/deprecated-generative-ai-js and a deprecation notice. We've noticed a couple bugs within the google genai implementation around stream parsing failures and would ask that this package is upgrade to the new, supported SDK.

Error Message and Stack Trace (if applicable)

No response

Description

See above.

System Info

"@langchain/google-genai": "^0.2.12",

[afirstenberg]

In the meantime, you may wish to evaluate switching to @langchain/google-gauth or @langchain/google-webauth

[Steffen911]

@afirstenberg Is that a suggestion to me or to whoever is taking this ticket?

[afirstenberg]

@Steffen911 - To you, or to anyone who is trying to use @langchain/google-genai at the moment.

[hntrl]

@Steffen911 Thanks for bringing this up, this is something that we get asked a lot about.

We don't like depending on a deprecated library to be clear. The reason that we didn't migrate to @google/genai sooner is because we had some hesitations on how google would be supporting this new package (deprecating a whole package is a little rash of a change for our taste -- we wanted to wait until the package had some time to bake). At some point we also tried upgrading to the genai library and there were some endemic complications with the upgrade that we had to sideline. There's a lot of good discussion surrounding this in #8393.

Just know this is something that's top of mind for us. For the record this is something that we'll come to a consensus very soon with our push to a v1 release of langchain. I'll keep this issue open until we get to that point for visibility, but unfortunately I don't have a quick fix for you.

[Steffen911]

@hntrl Thank you a lot for the additional context and for outlining the thought process! Unfortunately, Google has a habit of actions like this (https://killedbygoogle.com/ 🤦), so you have my full understanding.

I'll make sure to follow the PR discussion as well!

[afirstenberg]

@Steffen911 - Your concerns about Google library deprecation are also part of why the @langchain/google-webauth and @langchain/google-gauth libraries don't use any of the Gemini or AI libraries from Google, but make REST calls directly.

We've maintained them as cross platform for AI Studio API and Vertex API even at points where Google didn't, and when the API was updated for Gemini 2.0, we updated them before Google released a compatible JavaScript library for the new features.

You can see a bit more about these in this comment.

[beixiyo]

@google/generative-ai no thought process