MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-03-11 06:31:01 -07:00
Code Issues Packages Projects Releases Wiki Activity
Files
4002e980d9e02e973e19226dbc25aeec00a65cf5
gemini-cli/packages/cli/package.json

69 lines
2.3 KiB
JSON
Raw Normal View History

Initial commit of Gemini Code CLI This commit introduces the initial codebase for the Gemini Code CLI, a command-line interface designed to facilitate interaction with the Gemini API for software engineering tasks. The code was migrated from a previous git repository as a single squashed commit. Core Features & Components: * **Gemini Integration:** Leverages the `@google/genai` SDK to interact with the Gemini models, supporting chat history, streaming responses, and function calling (tools). * **Terminal UI:** Built with Ink (React for CLIs) providing an interactive chat interface within the terminal, including input prompts, message display, loading indicators, and tool interaction elements. * **Tooling Framework:** Implements a robust tool system allowing Gemini to interact with the local environment. Includes tools for: * File system listing (`ls`) * File reading (`read-file`) * Content searching (`grep`) * File globbing (`glob`) * File editing (`edit`) * File writing (`write-file`) * Executing bash commands (`terminal`) * **State Management:** Handles the streaming state of Gemini responses and manages the conversation history. * **Configuration:** Parses command-line arguments (`yargs`) and loads environment variables (`dotenv`) for setup. * **Project Structure:** Organized into `core`, `ui`, `tools`, `config`, and `utils` directories using TypeScript. Includes basic build (`tsc`) and start scripts. This initial version establishes the foundation for a powerful CLI tool enabling developers to use Gemini for coding assistance directly in their terminal environment. --- Created by yours truly: __Gemini Code__
2025-04-15 21:41:08 -07:00
{
infra: add multipackage support (#34)
2025-04-18 14:37:02 -07:00
"name": "@gemini-code/cli",
feat: publish docker image alongside npm package (#197)
2025-04-28 20:25:19 +00:00
"version": "0.1.0",
Update Gemini Code verbiage -> Gemini CLI - Did not update details that impact GC execution. Meaning packages are still named gemini-code (for now) and things that import them still import them as gemini-code.
2025-05-14 13:51:17 -07:00
"description": "Gemini CLI",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"type": "module",
refactor: clean up build output (#53) * refactor: clean up build output * refactor: add index.ts to package roots
2025-04-20 12:33:39 -07:00
"main": "dist/index.js",
feat: add alias to the cli bin directive (#126)
2025-04-23 01:04:34 +00:00
"bin": {
refactor: shorten 'gemini' binary name (#329)
2025-05-13 17:49:45 +00:00
"gemini": "dist/index.js"
feat: add alias to the cli bin directive (#126)
2025-04-23 01:04:34 +00:00
},
feat: publish docker image alongside npm package (#197)
2025-04-28 20:25:19 +00:00
"image": "us-west1-docker.pkg.dev/gemini-code-dev/gemini-code-containers/gemini-code-cli",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"scripts": {
feat: publish docker image alongside npm package (#197)
2025-04-28 20:25:19 +00:00
"build:sandbox": "DOCKER_BUILDKIT=1 docker build --build-arg CLI_VERSION=$npm_package_version --no-cache --secret id=npmrc,src=$HOME/.npmrc -t us-west1-docker.pkg.dev/gemini-code-dev/gemini-code-containers/gemini-code-cli:$npm_package_version -f Dockerfile.sandbox .",
shell bones (#160) * shell bones * Merge remote-tracking branch 'origin/main' into shell_bones * add line break * another line break * drop the log to avoid breaking terminals * rename tool to be consistent with terminal * fix build
2025-04-24 18:03:33 -07:00
"build": "../../scripts/build_package.sh",
feat: publish docker image alongside npm package (#197)
2025-04-28 20:25:19 +00:00
"publish:sandbox": "docker push us-west1-docker.pkg.dev/gemini-code-dev/gemini-code-containers/gemini-code-cli:$npm_package_version",
fix: add clean command to individual packages (#36)
2025-04-18 14:57:20 -07:00
"clean": "rm -rf dist",
fix: point 'npm run start' to index.js (#199)
2025-04-28 17:44:07 +00:00
"start": "node dist/index.js",
"debug": "node --inspect-brk dist/index.js",
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"lint": "eslint . --ext .ts,.tsx",
Adding some simple tests. (#54)
2025-04-19 18:07:24 +01:00
"format": "prettier --write .",
fix: point npmrc to dogfood artifact registry (#108)
2025-04-21 23:11:51 -07:00
"test": "vitest run",
feat: Enable CI test reporting and artifact management (#367)
2025-05-15 22:59:53 -07:00
"test:ci": "vitest run --reporter=junit --outputFile=junit.xml",
fix: Ensure filename is available for diff rendering in write-file This commit resolves a bug where the `write-file` operation could fail to render content due to a missing filename. The fix involves: - Ensuring `fileName` is consistently passed to `DiffRenderer.tsx` through `ToolConfirmationMessage.tsx`, `ToolMessage.tsx`, and `useGeminiStream.ts`. - Modifying `edit.ts` and `write-file.ts` to include `fileName` in the `FileDiff` object. - Expanding the `FileDiff` interface in `tools.ts` to include `fileName`. Additionally, this commit enhances the diff rendering by: - Adding syntax highlighting based on file extension in `DiffRenderer.tsx`. - Adding more language mappings to `getLanguageFromExtension` in `DiffRenderer.tsx`. - Added lots of tests for all the above. Fixes https://b.corp.google.com/issues/418125982
2025-05-15 23:51:53 -07:00
"typecheck": "tsc --noEmit",
feat: add flag to customize package version during pre-release staging (#155)
2025-04-24 20:02:49 +00:00
"prerelease:version": "node ../../scripts/bind_package_version.js",
"prerelease:deps": "node ../../scripts/bind_package_dependencies.js",
fix: remove --dry-run from cli prepublish script (#202)
2025-04-28 20:29:21 +00:00
"prepublishOnly": "npm publish --workspace=@gemini-code/server",
Ensure dogfood packaging more accurately mirrors local build. - Removed `build:package` in favor of `npm run build`. - The regular build does extra work to copy over relevant information into the `dist` dir. Alternatively without this we get a `dist` dir in the `cli` folder that has no seatbelt packaging. Fixes https://b.corp.google.com/issues/416634356
2025-05-08 23:49:02 -07:00
"prepack": "npm run build",
feat: publish docker image alongside npm package (#197)
2025-04-28 20:25:19 +00:00
"postpublish": "npm run build:sandbox && npm run publish:sandbox"
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
},
"files": [
"dist"
],
"dependencies": {
feat: publish docker image alongside npm package (#197)
2025-04-28 20:25:19 +00:00
"@gemini-code/server": "0.1.0",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"diff": "^7.0.0",
"dotenv": "^16.4.7",
Colorize code blocks. - This changeset uses lowlight.js to parse the code in codeblocks to derive an AST, it then translates that into CSS themes that are widely known via highlight.js (things that GitHub use), finally I translate those css.color attributes into Ink colors and effectivel do <Text color={the color}>the text</Text>. - To do this I needed to build color mappings from css -> Ink - I introduced a new `Theme` type that will be used to represent many different color themes. It also enabled the color mappings to be seamless. - Added a theme manager that only has one theme for now (VS2015). The theme works very well with our colorization. - Some other bits was removal of borders around our codeblocks since they now have richer rendering. - Most complex bits of code in this PR is in the `CodeColorizer.tsx` Fixes https://b.corp.google.com/issues/412433479
2025-04-22 18:37:58 -07:00
"highlight.js": "^11.11.1",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"ink": "^5.2.0",
Give Gemini Code a face lift. - This utilizes `ink-gradient` to render GEMINI CODE in amazing colors. - Added a shared color configuration for UX (should this be in config?). It's very possible that we shouldn't be talking about the specific colors and instead be mentioning "foreground"/"background"/inlineCode etc. type colors. - Updated existing color usages to utilize `Colors.*` Fixes https://b.corp.google.com/issues/411385593
2025-04-19 12:38:09 -04:00
"ink-gradient": "^3.0.0",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"ink-select-input": "^6.0.0",
"ink-spinner": "^5.0.0",
"ink-text-input": "^6.0.0",
Colorize code blocks. - This changeset uses lowlight.js to parse the code in codeblocks to derive an AST, it then translates that into CSS themes that are widely known via highlight.js (things that GitHub use), finally I translate those css.color attributes into Ink colors and effectivel do <Text color={the color}>the text</Text>. - To do this I needed to build color mappings from css -> Ink - I introduced a new `Theme` type that will be used to represent many different color themes. It also enabled the color mappings to be seamless. - Added a theme manager that only has one theme for now (VS2015). The theme works very well with our colorization. - Some other bits was removal of borders around our codeblocks since they now have richer rendering. - Most complex bits of code in this PR is in the `CodeColorizer.tsx` Fixes https://b.corp.google.com/issues/412433479
2025-04-22 18:37:58 -07:00
"lowlight": "^3.3.0",
feat(cli): Implement /bug command and add open dependency (#428)
2025-05-19 16:56:32 -07:00
"open": "^10.1.2",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"react": "^18.3.1",
feat: add CLI version number to footer (#134)
2025-04-23 22:00:40 +00:00
"read-package-up": "^11.0.0",
enable servers in sandbox to listen on localhost (127.0.0.1) instead of 0.0.0.0, ensuring servers can be container/host-agnostic (#207) * enable servers in sandbox to listen on localhost (127.0.0.1) instead of 0.0.0.0, ensuring servers can be container/host-agnostic * Merge remote-tracking branch 'origin/main' into sandbox_localhost_works
2025-04-28 18:40:24 -07:00
"shell-quote": "^1.8.2",
strip escape characters when pasting. (#386)
2025-05-16 13:17:48 -07:00
"string-width": "^7.1.0",
"strip-ansi": "^7.1.0",
allow comments in settings.json
2025-05-18 10:47:57 -07:00
"strip-json-comments": "^3.1.1",
strip escape characters when pasting. (#386)
2025-05-16 13:17:48 -07:00
"yargs": "^17.7.2"
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
},
"devDependencies": {
Fix an issue where types/react was a different version from our main … (#231) Co-authored-by: Brandon Keiji <brandonkeiji@google.com>
2025-04-30 16:33:43 -07:00
"@testing-library/react": "^14.0.0",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"@types/diff": "^7.0.2",
"@types/dotenv": "^6.1.1",
"@types/node": "^20.11.24",
Fix an issue where types/react was a different version from our main … (#231) Co-authored-by: Brandon Keiji <brandonkeiji@google.com>
2025-04-30 16:33:43 -07:00
"@types/react": "^18.3.1",
enable servers in sandbox to listen on localhost (127.0.0.1) instead of 0.0.0.0, ensuring servers can be container/host-agnostic (#207) * enable servers in sandbox to listen on localhost (127.0.0.1) instead of 0.0.0.0, ensuring servers can be container/host-agnostic * Merge remote-tracking branch 'origin/main' into sandbox_localhost_works
2025-04-28 18:40:24 -07:00
"@types/shell-quote": "^1.7.5",
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
"@types/yargs": "^17.0.32",
fix: Ensure filename is available for diff rendering in write-file This commit resolves a bug where the `write-file` operation could fail to render content due to a missing filename. The fix involves: - Ensuring `fileName` is consistently passed to `DiffRenderer.tsx` through `ToolConfirmationMessage.tsx`, `ToolMessage.tsx`, and `useGeminiStream.ts`. - Modifying `edit.ts` and `write-file.ts` to include `fileName` in the `FileDiff` object. - Expanding the `FileDiff` interface in `tools.ts` to include `fileName`. Additionally, this commit enhances the diff rendering by: - Adding syntax highlighting based on file extension in `DiffRenderer.tsx`. - Adding more language mappings to `getLanguageFromExtension` in `DiffRenderer.tsx`. - Added lots of tests for all the above. Fixes https://b.corp.google.com/issues/418125982
2025-05-15 23:51:53 -07:00
"ink-testing-library": "^4.0.0",
Fix an issue where types/react was a different version from our main … (#231) Co-authored-by: Brandon Keiji <brandonkeiji@google.com>
2025-04-30 16:33:43 -07:00
"jsdom": "^26.1.0",
Adding some simple tests. (#54)
2025-04-19 18:07:24 +01:00
"typescript": "^5.3.3",
"vitest": "^3.1.1"
Run `npm run format` - Also updated README.md accordingly. Part of https://b.corp.google.com/issues/411384603
2025-04-17 18:06:21 -04:00
},
"engines": {
"node": ">=18"
}
Initial commit of Gemini Code CLI This commit introduces the initial codebase for the Gemini Code CLI, a command-line interface designed to facilitate interaction with the Gemini API for software engineering tasks. The code was migrated from a previous git repository as a single squashed commit. Core Features & Components: * **Gemini Integration:** Leverages the `@google/genai` SDK to interact with the Gemini models, supporting chat history, streaming responses, and function calling (tools). * **Terminal UI:** Built with Ink (React for CLIs) providing an interactive chat interface within the terminal, including input prompts, message display, loading indicators, and tool interaction elements. * **Tooling Framework:** Implements a robust tool system allowing Gemini to interact with the local environment. Includes tools for: * File system listing (`ls`) * File reading (`read-file`) * Content searching (`grep`) * File globbing (`glob`) * File editing (`edit`) * File writing (`write-file`) * Executing bash commands (`terminal`) * **State Management:** Handles the streaming state of Gemini responses and manages the conversation history. * **Configuration:** Parses command-line arguments (`yargs`) and loads environment variables (`dotenv`) for setup. * **Project Structure:** Organized into `core`, `ui`, `tools`, `config`, and `utils` directories using TypeScript. Includes basic build (`tsc`) and start scripts. This initial version establishes the foundation for a powerful CLI tool enabling developers to use Gemini for coding assistance directly in their terminal environment. --- Created by yours truly: __Gemini Code__
2025-04-15 21:41:08 -07:00
}
Reference in New Issue Copy Permalink