chore(api): upgrade vite to v4

[johanbook]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @johanbook, 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 significant upgrade of the project's development dependencies, primarily advancing the vitest testing framework to its latest major version. This update cascades through various transitive dependencies, ensuring the project leverages the most current and optimized versions of its build and testing tools. The changes aim to improve overall development experience, performance, and maintainability by incorporating the latest features and security enhancements from these updated packages.

Highlights

• Vitest Major Version Upgrade: The testing framework vitest has been upgraded from version 3.2.4 to 4.0.18. This is a significant major version bump, bringing new features and potentially breaking changes, aligning with the latest advancements in the testing ecosystem.
• Coverage Tooling Update: The code coverage tool @vitest/coverage-v8 has also been updated from 3.2.4 to 4.0.18, ensuring compatibility and leveraging improvements alongside the main vitest upgrade.
• Transitive Dependency Updates: Numerous underlying dependencies, including @babel/parser, @babel/types, esbuild and its platform-specific binaries, magicast, std-env, tinyexec, and tinyrainbow, have been updated to their latest versions to support the new vitest release and other tooling.
• Dependency Clean-up and Streamlining: Several packages like @ampproject/remapping, cac, check-error, deep-eql, loupe, pathval, strip-literal, test-exclude, tinypool, and tinyspy have been removed from the dependency tree, indicating a streamlining or replacement of internal tooling and a more efficient dependency graph.
• Node.js Engine Requirement Adjustment: The minimum Node.js version required for vitest has been updated from ^18.0.0 || ^20.0.0 || >=22.0.0 to ^20.0.0 || ^22.0.0 || >=24.0.0, reflecting newer runtime expectations and ensuring compatibility with modern Node.js environments.

🧠 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

• services/api/package-lock.json
  • Updated vitest and @vitest/coverage-v8 to 4.0.18.
  • Updated @babel/parser from 7.28.4 to 7.29.0.
  • Updated @babel/types from 7.28.4 to 7.29.0.
  • Updated esbuild from 0.25.5 to 0.27.3, along with all its platform-specific optional dependencies.
  • Updated @jridgewell/sourcemap-codec from 1.5.0 to 1.5.5.
  • Updated @jridgewell/trace-mapping from 0.3.29 to 0.3.31.
  • Updated magicast from 0.3.5 to 0.5.2.
  • Updated @types/chai from 5.2.2 to 5.2.3.
  • Updated chai from 5.2.0 to 6.2.2.
  • Updated expect-type from 1.2.1 to 1.3.0.
  • Updated istanbul-reports from 3.1.7 to 3.2.0.
  • Updated std-env from 3.9.0 to 3.10.0.
  • Updated tinyexec from 0.3.2 to 1.0.2.
  • Updated tinyrainbow from 2.0.0 to 3.0.3.
  • Updated vite from 7.1.5 to 7.3.1.
  • Added @standard-schema/spec (1.1.0) and obug (2.1.1).
  • Removed @ampproject/remapping, cac, check-error, deep-eql, loupe, pathval, strip-literal, test-exclude, tinypool, and tinyspy.
  • Adjusted vitest's peer dependency for vite and its Node.js engine requirement.
• services/api/package.json
  • Updated vitest from 3.2.4 to 4.0.18.
  • Updated @vitest/coverage-v8 from 3.2.4 to 4.0.18.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

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

[gemini-code-assist]

Code Review

This pull request upgrades vitest to a new major version. However, the PR title is a bit misleading as it refers to vite instead of vitest. For a major dependency upgrade, it's also good practice to add a description with a link to the release notes to provide context on breaking changes. I've added a comment about a likely required configuration update that seems to be missing from this PR to ensure the upgrade is complete.

[gemini-code-assist]

This major version upgrade of vitest likely introduces breaking changes that require updates to configuration files. For example, recent versions of vitest recommend explicitly setting the coverage provider in vitest.config.ts. Based on the provided context, this configuration seems to be missing. Please ensure all necessary configuration changes for this new version of vitest are included in this PR to prevent breaking the test pipeline.