chore(deps): update dependency vite to v5.4.14

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
vite (source)	devDependencies	patch	5.4.12 -> 5.4.14

---

Release Notes

vitejs/vite (vite)

v5.4.14

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.13

Compare Source

Please refer to CHANGELOG.md for details.

---

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.

Summary by CodeRabbit

• Chores
  • Updated development dependency vite to version 5.4.14

[coderabbitai]

Walkthrough

This pull request involves a minor version update of the vite development dependency in the refarch-webcomponent project's package.json file. The change upgrades the Vite build tool from version 5.4.12 to 5.4.14, which likely includes bug fixes, performance improvements, or minor feature enhancements.

Changes

File	Change Summary
refarch-webcomponent/package.json	Updated vite dev dependency from 5.4.12 to 5.4.14

Possibly related PRs

• chore(deps): update dependency vite to v5.4.12 [security] #725: Previous vite dependency update from 5.4.11 to 5.4.12
• chore(deps): update dependency vite to v5.4.14 #734: vite dependency update in refarch-frontend from 5.4.12 to 5.4.14

Suggested labels

Template: Webcomponent

Suggested reviewers

• simonhir

Poem

🐰 A Vite update, small but neat,
Bumping numbers, version's sweet
From twelve to fourteen we ascend
Build tools progress without an end
Rabbit hops with coding glee! 🚀

---

📜 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 ce46dd4 and b9c5ec5.

⛔ 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: Verify compatibility of Vite 5.4.14.

The update from 5.4.12 to 5.4.14 is a patch version change that should be safe. Let's verify:

✅ Verification successful

✅ Vite 5.4.14 update is safe to proceed

The version is compatible with the project's Node.js requirements and all Vue plugins. No critical issues found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify Vite version compatibility and check for known issues

# Check if version exists and get release info
echo "Checking if version exists and getting release info..."
npm view vite@5.4.14 --json | jq '{version, engines, dependencies}'

# Check for any reported issues specific to this version
echo "Checking for issues specific to this version..."
gh api graphql -f query='
{
  search(query: "repo:vitejs/vite is:issue 5.4.14", type: ISSUE, first: 5) {
    nodes {
      ... on Issue {
        title
        state
        url
      }
    }
  }
}'

# Verify compatibility with Vue plugins
echo "Checking compatibility with Vue plugins..."
npm view @vitejs/plugin-vue@5.2.1 peerDependencies --json
npm view vite-plugin-vue-devtools@7.7.0 peerDependencies --json

Length of output: 1219

---

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

[devtobi]

LGTM