chore(deps): pnpm update chat

[KooshaPari]

User description

pnpm update

---

Note

Low Risk
Low risk since this is limited to dependency version bumps in chat, with no application logic changes; main risk is potential build or UI regressions from updated React/Storybook/Tailwind tooling.

Overview
Bumps agentapi-plusplus/chat dependencies and devDependencies, including React/React DOM, Radix UI components, react-dropzone, sonner, tailwind-merge, and tooling like Storybook, ESLint, Tailwind, and type packages.

^{Reviewed by Cursor Bugbot for commit 6b00f3b. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Update chat app dependencies and UI tooling versions

What Changed

• Updated the chat app’s core UI and runtime packages, including React, React DOM, Next, and several Radix UI components
• Updated Storybook, ESLint, Tailwind, and related type packages used for development and component previews
• Refreshed supporting packages for alerts, file upload, text areas, and styling utilities

Impact

✅ Fewer build breaks from dependency drift
✅ More reliable component previews in Storybook
✅ Smoother updates for the chat UI stack

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 57 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cb4bb7fa-abfa-476a-8e1e-4503f510be9f

📥 Commits

Reviewing files that changed from the base of the PR and between b5182b0 and 6b00f3b.

⛔ Files ignored due to path filters (1)

• agentapi-plusplus/chat/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• agentapi-plusplus/chat/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/pnpm-update-chat-2026-04-27

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 6b00f3b. Configure here.}

[cursor]

Stale bun and npm lockfiles after pnpm update

Medium Severity

The package.json version specifiers were updated but the bun.lock and package-lock.json lockfiles still contain the old specifiers (e.g., react: "^19.0.0" instead of "^19.2.5"). The project's README documents bun install as the development workflow, so bun.lock drift means developers will either get stale dependency versions or trigger unexpected lockfile modifications on install. A frozen-lockfile CI step would fail outright.

 

^{Reviewed by Cursor Bugbot for commit 6b00f3b. Configure here.}