chore: Update dependencies across website and browser packages

[yamadashy]

This PR updates dependencies across the website client, server, and browser packages to their latest versions.

Summary of Changes

Website Client Updates

• Update lucide-vue-next from 0.474.0 to 0.525.0
• Update rollup-plugin-visualizer from 6.0.1 to 6.0.3
• Update vite-plugin-pwa from 1.0.0 to 1.0.1

Website Server Updates

• Update @google-cloud/logging-winston from 6.0.0 to 6.0.1
• Update @hono/node-server from 1.13.8 to 1.16.0
• Update hono from 4.6.20 to 4.8.5
• Update repomix from 0.3.7 to 1.2.0
• Update @types/node from 22.13.0 to 24.0.14
• Update tsx from 4.19.2 to 4.20.3
• Update typescript from 5.7.3 to 5.8.3

Browser Extension Updates

• Update @biomejs/biome from 1.9.4 to 2.1.2
• Update @secretlint/secretlint-rule-preset-recommend from 9.3.1 to 10.2.1
• Update @types/chrome from 0.0.323 to 0.1.1
• Update @types/node from 22.10.2 to 24.0.14
• Update @types/webextension-polyfill from 0.10.7 to 0.12.3
• Update secretlint from 9.3.1 to 10.2.1
• Update sharp from 0.34.1 to 0.34.3
• Update tsx from 4.19.2 to 4.20.3
• Update vitest from 3.2.2 to 3.2.4

Checklist

• Run npm run test
• Run npm run lint

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Dependency versions have been updated in the package.json files for the browser, website/client, and website/server projects. Only version numbers of various dependencies and devDependencies were changed, with no modifications to scripts, configuration fields, or public API declarations.

Changes

File(s)	Change Summary
browser/package.json	Updated devDependencies to newer versions.
website/client/package.json	Updated lucide-vue-next, rollup-plugin-visualizer, and vite-plugin-pwa versions.
website/server/package.json	Updated dependencies and devDependencies to newer versions.

Possibly related PRs

• chore(deps): update all non-major dependencies #78: Updates overlapping development dependencies such as @biomejs/biome, typescript, and vitest in package.json files.
• chore(deps): Add configuration to make website PWA-ready #326: Adds PWA configuration and the vite-plugin-pwa dependency to website/client/package.json and related config files.
• Optimize website #317: Adds and configures the rollup-plugin-visualizer plugin in the website/client build setup.

Suggested labels

renovate, dependencies

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/website-update

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[claude]

Claude finished @yamadashy's task —— View job

---

Dependency Update Review

Todo List

• Read and analyze changed package.json files
• Review dependency updates for potential breaking changes
• Check for security vulnerabilities and compatibility issues
• Provide comprehensive review feedback

🔍 Code Review Feedback

This PR contains significant dependency updates across three packages. Here's my detailed analysis:

⚠️ Major Version Updates Requiring Attention

1. Browser Extension Critical Updates:

• @biomejs/biome: 1.9.4 → 2.1.2 - Major version jump likely includes breaking changes in linting rules
• @types/node: 22.10.2 → 24.0.14 - Major Node.js types update, may affect type definitions
• secretlint: 9.3.1 → 10.2.1 - Security linting tool major update, may have new rules

2. Website Server Critical Update:

• repomix: 0.3.7 → 1.2.0 - This is a major version jump for the core package. Given this is likely your own package, verify API compatibility
• @types/node: 22.13.0 → 24.0.14 - Same Node.js types concern as above

📝 Recommendations

1. Testing Strategy:
Following the repo's CLAUDE.md guidelines, ensure you run:

npm run lint  # In each package directory
npm run test  # In each package directory

2. Breaking Change Verification:

• @biomejs/biome 2.x: Check if new linting rules break existing code formatting
• Node.js types 24.x: Verify TypeScript compilation still works correctly
• secretlint 10.x: Ensure no new security violations are flagged
• repomix 1.2.0: Most critical - verify server functionality isn't broken

3. Browser Extension Engine Requirements:
Your browser extension specifies "node": ">=24.0.1" in engines, which aligns well with the @types/node update to 24.x.

✅ Positive Aspects

• Security: Updating secretlint to 10.x improves security scanning
• Consistency: All packages now use similar @types/node versions (24.x)
• Maintenance: Regular dependency updates prevent technical debt
• Patch Updates: Most website client updates are minor/patch (low risk)

🧪 Testing Recommendations

Given the scope of major version updates, I recommend:

1. Run full test suite in all three packages
2. Manual testing of browser extension functionality
3. Website deployment testing to ensure the repomix 1.2.0 update works correctly
4. Linting verification with the new biome 2.x rules

💡 Suggestions for Future

• Consider updating dependencies more frequently to avoid large batch updates
• Add automated testing for dependency updates in CI/CD
• Document any breaking changes from major version updates in commit messages

Summary

This is a comprehensive dependency update that addresses security and maintenance concerns. The major version updates require careful testing, particularly the repomix server dependency and biome linting rules. The PR structure and commit message follow the repository's conventions well.

---

[gemini-code-assist]

Summary of Changes

Hello @yamadashy, 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 focuses on a routine maintenance task: updating all project dependencies across the website client, website server, and browser extension packages. The goal is to ensure all components are running on the latest stable versions of their libraries, which typically brings improvements in security, performance, and access to new features. This is a standard chore PR to keep the codebase healthy and up-to-date.

Highlights

• Dependency Updates (Browser Extension): Updated several development dependencies for the browser extension, including @biomejs/biome, @secretlint/secretlint-rule-preset-recommend, @types/chrome, @types/node, @types/webextension-polyfill, secretlint, sharp, tsx, and vitest to their latest versions.
• Dependency Updates (Website Client): Updated client-side dependencies such as lucide-vue-next, rollup-plugin-visualizer, and vite-plugin-pwa to their latest stable releases.
• Dependency Updates (Website Server): Updated server-side dependencies including @google-cloud/logging-winston, @hono/node-server, hono, repomix, @types/node, tsx, and typescript to their newest versions.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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

[Copilot]

Pull Request Overview

This PR updates dependencies across the website and browser packages to their latest versions, focusing on minor and patch version updates for improved functionality and security.

• Updates dependencies in website client, server, and browser extension packages
• Includes significant version updates for TypeScript (5.7.3 → 5.8.3), Hono framework (4.6.20 → 4.8.5), and Biome linter (1.9.4 → 2.1.2)
• Updates Node.js types from v22 to v24 across multiple packages

Reviewed Changes

Copilot reviewed 3 out of 6 changed files in this pull request and generated 4 comments.

File	Description
website/server/package.json	Updates server dependencies including Hono, Google Cloud logging, and development tools
website/client/package.json	Updates client dependencies for Vue icons, Vite plugins, and build tools
browser/package.json	Updates browser extension dependencies including linting tools, TypeScript types, and testing frameworks

Files not reviewed (3)

• browser/package-lock.json: Language not supported
• website/client/package-lock.json: Language not supported
• website/server/package-lock.json: Language not supported

[cloudflare-workers-and-pages]

Deploying repomix with    Cloudflare Pages

Latest commit:	d1ff4e9
Status:	✅  Deploy successful!
Preview URL:	https://b98592f0.repomix.pages.dev
Branch Preview URL:	https://feat-website-update.repomix.pages.dev

View logs

[gemini-code-assist]

Code Review

This PR updates a significant number of dependencies across the website and browser packages, including several major version bumps. While dependency updates are crucial for security and performance, major version changes can introduce breaking changes. It's important to ensure that these updates don't negatively impact the application's functionality. Please make sure to run all tests and perform manual verification, especially for the browser extension and the server logic that relies on repomix.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.23%. Comparing base (02c1150) to head (d1ff4e9).
Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #738   +/-   ##
=======================================
  Coverage   90.23%   90.23%           
=======================================
  Files         100      100           
  Lines        5768     5768           
  Branches     1205     1205           
=======================================
  Hits         5205     5205           
  Misses        563      563           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.