fix(ui): add missing zod production dependency

[itsmylife44]

Summary

Fixes production build failure caused by missing zod dependency in UI package.

Problem

The terminal route (src/routes/terminal.tsx) uses zod for search parameter validation:

import { z } from 'zod';

const terminalSearchSchema = z.object({
  cwd: z.string().optional(),
  // ...
});

However, zod was not listed as a direct dependency in apps/ui/package.json. During development, it was available as a transitive dependency, but the production build fails:

Rollup failed to resolve import "zod" from "src/routes/terminal.tsx"

Solution

Add zod as an explicit production dependency in apps/ui/package.json.

Changes

• apps/ui/package.json: Add "zod": "^3.24.1" to dependencies
• package-lock.json: Updated accordingly

Testing

• Production build (npm run build) completes successfully
• UI functions correctly with zod validation

Summary by CodeRabbit

• Chores
  • Updated project dependencies to support enhanced functionality.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @itsmylife44, 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 addresses a critical production build failure in the UI package by correctly declaring zod as a direct dependency. This ensures that the UI application can be built successfully and continues to leverage zod for robust search parameter validation, preventing future build-related disruptions.

Highlights

• Dependency Management: The zod library has been explicitly added as a production dependency to the apps/ui package. Previously, zod was used in src/routes/terminal.tsx but was only available as a transitive dependency, leading to production build failures.
• Build Fix: This change resolves the production build failure that occurred because the zod import could not be resolved during the build process for the UI application.

🧠 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.

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. ↩

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds the zod runtime dependency (version ^3.24.1) to the UI package's dependency manifest, enabling import resolution for zod-dependent modules within the UI application.

Changes

Cohort / File(s)	Summary
Dependency Addition apps/ui/package.json	Added zod ^3.24.1 as a runtime dependency to resolve missing package imports.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• Docker Build Fails: Missing zod dependency and spec-parser in Dockerfile #674: Directly addresses missing zod dependency in apps/ui/package.json required for import resolution in terminal.tsx.

Possibly related PRs

• fix: docker, broken npm build script and missing dependency #664: Performs the same zod dependency addition to apps/ui/package.json with identical intent.

Suggested labels

Bug

Poem

🐰 A tiny hop, a single line,
Zod joins the fold, now code feels fine,
No more imports left in the dark,
One small change, one giant spark!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix(ui): add missing zod production dependency' accurately describes the main change in the PR: adding zod as an explicit production dependency to fix a missing import issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request correctly identifies and fixes a production build failure by adding the missing zod dependency to the UI package. My review includes two main points: first, I've noted a discrepancy in zod versions across the monorepo and suggested aligning them to prevent potential conflicts. Second, the PR includes undocumented version bumps for several packages, and I've recommended either documenting this change or handling it in a separate PR to maintain a clear commit history. Overall, the core fix is sound, and these suggestions aim to improve the project's long-term maintainability.

[gemini-code-assist]

This change introduces zod@^3.24.1. However, other parts of the monorepo appear to be using zod@4.x (version 4.2.1 is present in the lockfile, likely for the @modelcontextprotocol/sdk dependency). Using two different major versions of zod (v3 and v4) can lead to hard-to-debug type incompatibilities, especially if Zod schemas or inferred types are shared between packages like the UI and the server.

To ensure consistency and prevent future issues, it's highly recommended to use a single version of zod across the project. Please consider aligning on a single version, preferably by upgrading this dependency to v4 to match what's already in use elsewhere in the repository.

Suggested change

	"zod": "^3.24.1",
	"zod": "^4.2.1",

[gemini-code-assist]

This PR includes version bumps for several packages (e.g., from 0.12.0rc to 0.13.0), which seems to go beyond the scope of the fix(ui) commit message. To keep the commit history clean and understandable, it's better to separate dependency fixes from version bumps.

Could you please consider either:

1. Updating the PR title and description to reflect the version bump (e.g., release: v0.13.0).
2. Reverting the version bumps and handling them in a separate release PR.