chore(deps): update dependency vitest to v3.0.4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
vitest (source)	devDependencies	patch	3.0.3 -> 3.0.4

---

Release Notes

vitest-dev/vitest (vitest)

v3.0.4

Compare Source

   🐞 Bug Fixes

• Filter projects eagerly during config resolution  -  by @​sheremet-va and @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7313 (dff44)
• Apply development &nbsp;-&nbsp; by @&#8203;hi-ogawa and @&#8203;sheremet-va [<samp>(produ)</samp>](https://redirect.github.com/vitest-dev/vitest/commit/production condition on Vite 6 (#​7301))
• browser: Restrict served files from /__screenshot-error  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7340 (ed9ae)
• deps: Update all non-major dependencies  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7297 (38ea8)
• runner: Timeout long sync hook  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7289 (c60ee)
• typechecking: Support typechecking parsing with Vite 6  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7335 (bff70)
• types: Fix public types  -  by @​mrginglymus and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7328 (ce6af)

    View changes on GitHub

---

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 vitest dependency to version 3.0.4

[coderabbitai]

Walkthrough

This pull request involves a minor version update of the vitest dependency in the refarch-webcomponent/package.json file, incrementing the version from 3.0.3 to 3.0.4. The change is a small, targeted update to a testing library version with no other modifications to the project configuration.

Changes

File	Change Summary
refarch-webcomponent/package.json	Updated vitest dependency version from 3.0.3 to 3.0.4

Possibly related PRs

• chore(deps): update dependency vite to v5.4.14 #735: Updates vitest dependency in the same package.json from 3.0.3 to 3.0.4
• chore(deps): update dependency vite to v6 #740: Previous vitest version upgrade from 2.1.8 to 3.0.3

Suggested labels

Template: Webcomponent

Suggested reviewers

• devtobi

Poem

🐰 A tiny version hop, so neat
Vitest updates, a testing treat
From 3.0.3 to 3.0.4 we go
A rabbit's leap of code, just so!
Small change, big smile 🧪✨

---

📜 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 f417dcf and 0a438eb.

⛔ 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)

39-39: LGTM! The vitest update looks safe to merge.

The update from v3.0.3 to v3.0.4 is a patch release containing bug fixes and improvements. The changes are particularly relevant for this project as they include enhanced support for Vite 6, which this project uses.

Let's verify the compatibility with the current setup:

✅ Verification successful

Verified: The vitest update is safe to apply ✅

The verification of both components' test setups confirms that:

• Both projects use standard vitest APIs and configurations
• The test environments are properly configured
• No compatibility issues were found between vitest 3.0.4 and the current setup

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify vitest compatibility with current dependencies

# Check if package-lock.json exists and contains any peer dependency warnings
if [ -f package-lock.json ]; then
  echo "Checking package-lock.json for peer dependency warnings..."
  cat package-lock.json | jq -r '.packages | .[] | select(.peerDependencies != null) | select(.name == "vitest")'
fi

# Check if there are any GitHub issues reporting compatibility problems between vitest 3.0.4 and Vite 6
gh api graphql -f query='
{
  search(query: "repo:vitest-dev/vitest is:issue state:open vitest 3.0.4 vite 6", type: ISSUE, first: 5) {
    nodes {
      ... on Issue {
        title
        url
        labels(first: 5) {
          nodes {
            name
          }
        }
      }
    }
  }
}'

Length of output: 474

---

Script:

#!/bin/bash
# Check for lock files and test setup
echo "=== Checking for lock files ==="
ls -la *.lock pnpm-lock.yaml 2>/dev/null || echo "No lock files found"

echo -e "\n=== Checking for vitest config ==="
fd -e js -e ts -e mjs "vitest.config" || echo "No vitest config found"

echo -e "\n=== Checking for test files ==="
fd -e spec.ts -e spec.js -e test.ts -e test.js || echo "No test files found"

echo -e "\n=== Checking package.json test script ==="
if [ -f package.json ]; then
    jq '.scripts.test' package.json
fi

Length of output: 694

---

Script:

#!/bin/bash
echo "=== Checking vitest config content ==="
for config in refarch-frontend/vitest.config.ts refarch-webcomponent/vitest.config.ts; do
    echo -e "\nContent of $config:"
    cat "$config"
done

echo -e "\n=== Checking test file content ==="
for test in refarch-frontend/tests/unit/example.spec.ts refarch-webcomponent/tests/unit/example.spec.ts; do
    echo -e "\nContent of $test:"
    cat "$test"
done

Length of output: 3152

---

🪧 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