Skip to content

fix(js): duplicate sample project names#4578

Merged
yesudeep merged 1 commit intomainfrom
yesudeep/fix/absorbing-wing
Feb 12, 2026
Merged

fix(js): duplicate sample project names#4578
yesudeep merged 1 commit intomainfrom
yesudeep/fix/absorbing-wing

Conversation

@yesudeep
Copy link
Contributor

@yesudeep yesudeep commented Feb 11, 2026

This PR updates the package.json names for several JS test apps to resolve duplicate project name issues.

Changes

  • Renamed failing test apps to have unique package names:
    • js/testapps/ollama: basic-gemini -> basic-ollama
    • js/testapps/rag: rag -> rag-testapp
    • js/testapps/vertexai-vector-search-bigquery: vertex-vector-search -> vertex-vector-search-bigquery
    • js/testapps/vertexai-vector-search-custom: vertex-vector-search -> vertex-vector-search-custom
    • js/testapps/vertexai-vector-search-firestore: vertex-vector-search -> vertex-vector-search-firestore

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @yesudeep, I'm Gemini Code Assist1! 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 resolves naming inconsistencies across various JavaScript test applications by updating their package.json name fields. The changes ensure that each sample project has a distinct and more informative name, improving clarity and preventing potential conflicts when managing or installing these packages.

Highlights

  • Duplicate Project Names Fixed: Addressed an issue where several JavaScript sample projects had duplicate or generic names in their package.json files, leading to potential conflicts or confusion.
  • Unique Naming Convention Applied: Updated the name field in package.json for multiple test applications to ensure each project has a unique and descriptive identifier, often by incorporating the directory name or specific technology.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • js/testapps/ollama/package.json
    • Updated the project name from "basic-gemini" to "basic-ollama".
  • js/testapps/rag/package.json
    • Updated the project name from "rag" to "rag-testapp".
  • js/testapps/vertexai-vector-search-bigquery/package.json
    • Updated the project name from "vertex-vector-search" to "vertex-vector-search-bigquery".
  • js/testapps/vertexai-vector-search-custom/package.json
    • Updated the project name from "vertex-vector-search" to "vertex-vector-search-custom".
  • js/testapps/vertexai-vector-search-firestore/package.json
    • Updated the project name from "vertex-vector-search" to "vertex-vector-search-firestore".
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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses an issue with duplicate project names across several package.json files for the JavaScript test applications. The changes correctly update the name field in each file to be unique and more descriptive of the specific test app's purpose. This is a good practice that improves maintainability and prevents potential package name conflicts. The changes are accurate and well-contained.

@yesudeep yesudeep force-pushed the yesudeep/fix/absorbing-wing branch from 36f833a to d807631 Compare February 11, 2026 12:44
@yesudeep yesudeep requested review from pavelgj and removed request for MengqinShen, huangjeff5 and zarinn3pal February 11, 2026 12:44
@yesudeep yesudeep enabled auto-merge (squash) February 11, 2026 12:45
@yesudeep yesudeep requested a review from huangjeff5 February 12, 2026 22:25
@yesudeep yesudeep merged commit 98943f6 into main Feb 12, 2026
6 checks passed
@yesudeep yesudeep deleted the yesudeep/fix/absorbing-wing branch February 12, 2026 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants