# How to propose a feature request and contribute to @langchain/google-genai?
**URL:** https://forum.langchain.com/t/how-to-propose-a-feature-request-and-contribute-to-langchain-google-genai/2580
**Category:** LangChain
**Tags:** js-help, feature-request
**Created:** [December 22, 2025, 7:46am UTC](https://forum.langchain.com/t/how-to-propose-a-feature-request-and-contribute-to-langchain-google-genai/2580 "2025-12-22T07:46:14Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@recrash](https://forum.langchain.com/u/recrash)
#### Post date: [December 22, 2025, 7:46am UTC](https://forum.langchain.com/t/how-to-propose-a-feature-request-and-contribute-to-langchain-google-genai/2580/1 "2025-12-22T07:46:15Z")
Hi everyone,
I’ve been happy user of `langchainjs`, and I am now looking to make my very first contribution to the open-source community. Please bear with me if I’m not following the exact protocol.
I noticed that the GitHub Issues section is primarily for bug reports, and it directed me here to this forum for feature requests. I have a specific improvement in mind regarding `@langchain/google-genai`:
**The Proposal:** Currently, to set the `TaskType` option for embeddings, users are forced to manually install and import the `@google/generative-ai` package separately. However, as Google has officially deprecated the `@google/generative-ai` SDK, it feels counterintuitive to require this as an extra dependency just for a few Enums.
I believe it would be much better to export those Enums (like `TaskType`) directly from `@langchain/google-genai` to streamline the developer experience and remove the need for a deprecated peer dependency.
I would be thrilled to work on this and contribute the code myself. Is this the right place to discuss this, and would the team be open to an issue for this request?
I’d love to hear your guidance on how I can proceed with this contribution.
---
### Author:  [@coawazie](https://forum.langchain.com/u/coawazie)
#### Post date: [December 22, 2025, 3:57pm UTC](https://forum.langchain.com/t/how-to-propose-a-feature-request-and-contribute-to-langchain-google-genai/2580/2 "2025-12-22T15:57:33Z")
Imports such as `import {GoogleGenAI, HarmBlockThreshold, HarmCategory, SafetySetting} from "@google/genai";`are now also throwing errors with configs for instantiating `ChatGoogleGenerativeAI`. I think Google was going for backward compatibility when they mapped the `category` and `threshold` config params in their new SDK to string ([new genai sdk](https://ai.google.dev/gemini-api/docs/migrate#javascript_14)) to the enums in their _ **legacy** _ SDK. But depending on runtime Javascript not enforcing types is too brittle, and Typescript will ordinarily throw on this. Using `@ts-expect-error: legacy` also is a non-ideal workaround as this is Google we are talking about here, and we know _breaking changes_ is what they do!