chore(deps): update development dependencies

[z0ffy]

Update multiple development dependencies to their latest versions:

• @eslint/js: 9.29.0 → 9.32.0
• @types/node: 24.0.3 → 24.2.0
• @vitest/coverage-v8: 3.2.3 → 3.2.4
• eslint: 9.29.0 → 9.32.0
• globals: 16.2.0 → 16.3.0
• lint-staged: 16.1.2 → 16.1.4
• typescript: 5.8.3 → 5.9.2
• typescript-eslint: 8.34.1 → 8.39.0
• vite: 7.0.0 → 7.1.0
• vitest: 3.2.3 → 3.2.4

Summary by Sourcery

Bump various development dependencies across linting, build, and test toolchains to their latest versions.

Enhancements:

• Update linting dependencies including ESLint, @eslint/js, @typescript-eslint, @stylistic/eslint-plugin, commitlint, globals, and lint-staged
• Upgrade TypeScript to 5.9.2 along with related tooling such as tsup, jiti, and cosmiconfig loader
• Bump build and bundling tools: Vite to 7.1.0, Rollup to 4.46.2, esbuild to 0.25.8, and associated plugins
• Update testing framework Vitest to 3.2.4 and its coverage, expect, runner, snapshot, mocker, and utils packages

[sourcery-ai]

Reviewer's Guide

This PR updates key development dependencies to their latest releases and regenerates the lockfile to reflect those version bumps across all transitive packages.

File-Level Changes

Change	Details	Files
Dev dependencies bumped in package.json	Updated @eslint/js, eslint to 9.32.0 Updated @types/node to 24.2.0 Updated typescript to 5.9.2 and typescript-eslint to 8.39.0 Updated vite to 7.1.0 and vitest (with coverage-v8) to 3.2.4 Updated globals, lint-staged, and other lint/test tools	package.json pnpm-lock.yaml
Lockfile regenerated for platform-specific builds and sub-dependencies	Bumped esbuild to 0.25.8 with all platform binaries Upgraded rollup to 4.46.2 and its platform plugins Updated jiti to 2.5.1 and cosmiconfig TypeScript loader Propagated TypeScript version (5.9.2) through @typescript-eslint and ts-api-utils entries Refreshed Vitest sub-packages (expect, runner, snapshot, spy, utils) to 3.2.4	pnpm-lock.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @z0ffy - I've reviewed your changes - here's some feedback:

• Consider splitting this massive lockfile update into smaller, focused PRs (e.g. ESLint-related, Vitest-related, TypeScript-related) to make reviewing and troubleshooting easier.
• Verify that the newly added optional target @esbuild/openharmony-arm64 is actually needed—if you’re not targeting OpenHarmony, removing it will keep the lockfile leaner.
• Some upgraded dev tools (e.g. listr2@9.x, lint-staged@16.1.4) now require Node >= 20 per their engines field; please confirm our CI and project engines align with these new requirements.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Consider splitting this massive lockfile update into smaller, focused PRs (e.g. ESLint-related, Vitest-related, TypeScript-related) to make reviewing and troubleshooting easier.
- Verify that the newly added optional target `@esbuild/openharmony-arm64` is actually needed—if you’re not targeting OpenHarmony, removing it will keep the lockfile leaner.
- Some upgraded dev tools (e.g. listr2@9.x, lint-staged@16.1.4) now require Node >= 20 per their engines field; please confirm our CI and project engines align with these new requirements.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}