chore: upgrading swc, biome, vitest, and rimraf

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing and Code of Conduct guidelines.
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
chore: upgrading swc, biome, vitest, and rimraf

[gemini-code-assist]

Summary of Changes

Hello, 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 maintaining the project's health and performance by updating several core development dependencies to their latest stable versions. These updates bring improvements, bug fixes, and potentially new features from the respective tools, ensuring the project benefits from the most recent advancements in code formatting, transpilation, testing, and file system operations.

Highlights

• Dependency Upgrades: Upgraded @biomejs/biome from 2.3.14 to 2.4.7, @swc/core from 1.15.11 to 1.15.18, @vitest/coverage-v8 from 4.0.18 to 4.1.0, rimraf from 6.1.2 to 6.1.3, and vitest from 4.0.18 to 4.1.0.
• Lockfile Synchronization: The pnpm-lock.yaml file was updated to reflect the new versions of direct and transitive dependencies, ensuring consistent installations across environments.

Changelog

• package.json
  • Updated @biomejs/biome from ^2.3.14 to ^2.4.7
  • Updated @swc/core from ^1.15.11 to ^1.15.18
  • Updated @vitest/coverage-v8 from ^4.0.18 to ^4.1.0
  • Updated rimraf from ^6.1.2 to ^6.1.3
  • Updated vitest from ^4.0.18 to ^4.1.0
• pnpm-lock.yaml
  • Updated locked versions for @biomejs/biome and its platform-specific CLI binaries.
  • Updated locked versions for @swc/core and its platform-specific binaries.
  • Updated locked versions for @vitest/coverage-v8, @vitest/expect, @vitest/mocker, @vitest/pretty-format, @vitest/runner, @vitest/snapshot, @vitest/spy, and @vitest/utils.
  • Updated locked version for rimraf.
  • Updated locked version for vitest.
  • Updated various @esbuild/* packages from 0.27.3 to 0.27.4.
  • Updated various @rollup/* packages from 4.57.1 to 4.59.0.
  • Updated acorn from 8.15.0 to 8.16.0.
  • Updated ast-v8-to-istanbul from 0.3.11 to 1.0.0.
  • Added new dependency balanced-match@4.0.4.
  • Added new dependency brace-expansion@5.0.4.
  • Added new dependency convert-source-map@2.0.0.
  • Updated es-module-lexer from 1.7.0 to 2.0.0.
  • Updated esbuild from 0.27.3 to 0.27.4.
  • Added new dependency glob@13.0.6.
  • Updated lru-cache from 11.2.4 to 11.2.7.
  • Added new dependency minimatch@10.2.4.
  • Updated minipass from 7.1.2 to 7.1.3.
  • Added new dependency path-scurry@2.0.2 and updated path-scurry@2.0.1 dependencies.
  • Updated postcss from 8.5.6 to 8.5.8 and related postcss-* packages.
  • Updated rollup from 4.57.1 to 4.59.0.
  • Updated std-env from 3.10.0 to 4.0.0.
  • Updated tinyexec from 1.0.2 to 1.0.4.
  • Updated tinyrainbow from 3.0.3 to 3.1.0.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (4b5fd22) to head (1db42ea).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #127   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           37        37           
  Lines         1044      1044           
  Branches       208       208           
=========================================
  Hits          1044      1044           

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

[gemini-code-assist]

Code Review

This pull request upgrades several development dependencies. While most upgrades are minor or patch versions, the update to vitest introduces major version bumps for several of its transitive dependencies, such as std-env, ast-v8-to-istanbul, and es-module-lexer. These major upgrades could potentially introduce breaking changes. I've added comments to highlight these specific changes in pnpm-lock.yaml.