feat(genai): live samples part2

[Guiners]

Description

Fixes #

Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.

Checklist

• I have followed guidelines from CONTRIBUTING.MD and Samples Style Guide
• Tests pass: npm test (see Testing)
• Lint pass: npm run lint (see Style)
• Required CI tests pass (see CI testing)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• This pull request is from a branch created directly off of GoogleCloudPlatform/nodejs-docs-samples. Not a fork.
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new sample directory, and I created GitHub Actions workflow for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

Note: Any check with (dev), (experimental), or (legacy) can be ignored and should not block your PR from merging (see CI testing).

[snippet-bot]

Here is the summary of changes.

You are about to add 5 region tags.

• genai/live/live-audio-with-txt.js:15, tag googlegenaisdk_live_audio_with_txt
• genai/live/live-ground-ragengine-with-txt.js:15, tag googlegenaisdk_live_ground_ragengine_with_txt
• genai/live/live-structured-ouput-with-txt.js:15, tag googlegenaisdk_live_structured_output_with_txt
• genai/live/live-transcribe-with-audio.js:15, tag googlegenaisdk_live_transcribe_with_audio
• genai/live/live-txt-with-audio.js:15, tag googlegenaisdk_live_txt_with_audio

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[gemini-code-assist]

Summary of Changes

Hello @Guiners, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly expands the Google GenAI SDK samples by adding a suite of 'live' interaction examples. These new samples cover a range of real-time use cases, including generating audio from text, leveraging RAG for grounded responses, extracting structured data, transcribing audio, and generating text from audio. The additions aim to provide developers with practical demonstrations of the SDK's capabilities for building dynamic and interactive AI applications.

Highlights

• New Live GenAI Samples: This pull request introduces five new live samples for the Google GenAI SDK, showcasing various real-time interaction capabilities.
• Audio Generation from Text: A new sample, live-audio-with-txt.js, demonstrates how to generate audio responses from text input within a live GenAI session.
• Grounded Text with RAG Engine: The live-ground-ragengine-with-txt.js sample illustrates using a Retrieval Augmented Generation (RAG) engine with a memory corpus for grounded text responses in a live GenAI session.
• Structured Output Extraction: A new sample, live-structured-ouput-with-txt.js, provides an example of extracting structured JSON output from text input using the GenAI model.
• Audio Transcription: The live-transcribe-with-audio.js sample shows how to transcribe audio input into text using a live GenAI model.
• Text Generation from Audio: A new sample, live-txt-with-audio.js, demonstrates generating text responses in a live GenAI session from audio input.
• Dependency Updates: Required dependencies such as google-auth-library, node-fetch, and openai have been added or updated in genai/package.json and the root package.json to support these new functionalities.
• Comprehensive Testing: Each new live sample is accompanied by a dedicated test file to ensure functionality and provide examples of usage.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds several new live samples for the GenAI SDK, demonstrating features like audio generation, RAG, structured output, and transcription. The changes are well-structured, but I've found a few areas for improvement, mainly around code clarity and correctness. There are some minor code style issues that can be addressed, and one of the new tests is critically flawed and needs to be rewritten. Please see my detailed comments below.

[cfloress]

Same comment that @jdomingr that applies in a few files, once that is solved will LGTM