⬆️ chore(deps): Update devDependency vite-tsconfig-paths to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite-tsconfig-paths	4.3.2 -> 5.1.4

---

Release Notes

aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)

v5.1.4

Compare Source

• fix: correctly infer the paths root dir (eea1c17) (#​150)

v5.1.3

Compare Source

• fix: Once an importer is matched, end directory traversal (b0d8ecb)
• feat: Add vite-tsconfig-paths:resolve debug logs (7160d6e)
• chore: Ensure debug logs can be enabled in vitest (0dc9a8b)

v5.1.2

Compare Source

• fix Windows regression introduced in v5.1.1 (#​162)

v5.1.1

Compare Source

• support ${configDir} syntax in include/exclude (#​156)

v5.1.0

Compare Source

• Add skip option for adding additional directories to be skipped when searching for tsconfig.json files (#​146)
• Fix path resolution on Windows when other Vite plugins neglect to normalize the importer path before calling this.resolve in their resolveId hooks (#​157)
• Allow both tsconfig.json and jsconfig.json in the same directory (4124b09)

v5.0.1

Compare Source

v5.0.0

Compare Source

This package is now ESM only in order to align with Vite: https://vitejs.dev/guide/migration#deprecate-cjs-node-api

If your project is using CommonJS, you can rename your Vite config to use the .mjs or .mts extension (depending on whether you use TypeScript or not). If you're not using Vite v5.0.0+, you may want to pin your dependency to v4 of this plugin.

---

Configuration

📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - "before 4am" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
repository-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 10, 2025 2:45pm

[coderabbitai]

Important

Review skipped

Bot user detected.

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

The recent changes involve updating the vite-tsconfig-paths package from version 4.3.2 to 5.0.1 in both the main and repository package.json files. This upgrade is expected to enhance functionality, improve performance, and ensure better compatibility in TypeScript path resolution for Vite projects. The update aims to streamline dependency management without altering other configurations.

Changes

Files	Change Summary
package.json, packages/repository/...	Updated vite-tsconfig-paths from 4.3.2 to 5.0.1

Poem

Hop along, let’s cheer and play,
A version change, hip-hip-hooray! 🐇✨
From four to five, we leap so high,
For paths resolved, we touch the sky!
Bugs be gone, let’s dance and sing,
In Vite’s embrace, new joys we bring! 🎉

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• 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.
• 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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6086250 and 92d02a0.

Files ignored due to path filters (1)

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

Files selected for processing (2)

• package.json (1 hunks)
• packages/repository/package.json (1 hunks)

Additional comments not posted (2)

package.json (1)

44-44: Version update approved. Ensure compatibility.

The update of vite-tsconfig-paths to version 5.0.0 is approved.

However, verify that the new version is compatible with the existing codebase and does not introduce any breaking changes.

packages/repository/package.json (1)

64-64: Version update approved. Ensure compatibility.

The update of vite-tsconfig-paths to version 5.0.0 is approved.

However, verify that the new version is compatible with the existing codebase and does not introduce any breaking changes.

[github-actions]

Coverage Report for packages/repository

Status	Category	Percentage	Covered / Total
🟢	Lines	96.83% (🎯 80%)	153 / 158
🟢	Statements	97.02% (🎯 80%)	163 / 168
🟢	Functions	95.71% (🎯 80%)	67 / 70
🟢	Branches	92.47% (🎯 80%)	86 / 93

File Coverage

No changed files found.

Generated in workflow #324 for commit de27e02 by the Vitest Coverage Report Action

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 92d02a0 and c8016b0.

Files ignored due to path filters (1)

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

Files selected for processing (2)

• package.json (1 hunks)
• packages/repository/package.json (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• package.json
• packages/repository/package.json