chore(deps): update dependency vite to v6.1.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
vite (source)	devDependencies	patch	6.1.0 -> 6.1.1

---

Release Notes

vitejs/vite (vite)

v6.1.1

Compare Source

• fix: ensure .[cm]?[tj]sx? static assets are JS mime (#​19453) (e7ba55e), closes #​19453
• fix: ignore *.ipv4 address in cert (#​19416) (973283b), closes #​19416
• fix(css): run rewrite plugin if postcss plugin exists (#​19371) (bcdb51a), closes #​19371
• fix(deps): bump tsconfck (#​19375) (746a583), closes #​19375
• fix(deps): update all non-major dependencies (#​19392) (60456a5), closes #​19392
• fix(deps): update all non-major dependencies (#​19440) (ccac73d), closes #​19440
• fix(html): ignore malformed src attrs (#​19397) (aff7812), closes #​19397
• fix(worker): fix web worker type detection (#​19462) (edc65ea), closes #​19462
• refactor: remove custom .jxl mime (#​19457) (0c85464), closes #​19457
• feat: add support for injecting debug IDs (#​18763) (0ff556a), closes #​18763
• chore: update 6.1.0 changelog (#​19363) (fa7c211), closes #​19363

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[coderabbitai]

Walkthrough

The pull request updates the vite dependency in the refarch-webcomponent/package.json file. The version is incremented from 6.1.0 to 6.1.1, signifying a minor update that typically includes bug fixes or small improvements without breaking changes.

Changes

File	Change Summary
refarch-webcomponent/package.json	Updated the vite dependency version from 6.1.0 to 6.1.1 in devDependencies.

Possibly related PRs

• chore(deps): update dependency vite to v6.1.0 #772: Updates the vite dependency (from 6.0.11 to 6.1.0), which is directly related to the change in this PR.
• chore(deps): update dependency vite to v6 #740: Modifies the vite dependency from 5.4.14 to 6.0.11, showing a progression consistent with this update.
• chore(deps): update dependency vite to v6 #738: Also addresses a vite dependency version update, aligning with the modifications made here.

Suggested reviewers

• devtobi

Poem

I'm a little rabbit, hopping through the code,
I found a tiny update on a dependency road.
From 6.1.0 to 6.1.1, with a joyful flip,
My whiskers twitch in every bug fix tip.
Code so neat and sweet, it makes my heart skip—
A happy hop for every update on this trip!
🐰🌟

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3106fbe and 2a93d27.

⛔ Files ignored due to path filters (1)

• refarch-webcomponent/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• refarch-webcomponent/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build (refarch-backend)

🔇 Additional comments (1)

refarch-webcomponent/package.json (1)

37-37: Vite Version Update: 6.1.1

The dependency update from version 6.1.0 to 6.1.1 incorporates the minor bug fixes and improvements as noted in the release notes. Since this is a patch update, it should be backward compatible. Please ensure that integration tests are executed to catch any unforeseen issues arising from the update.

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.