Update README.md

[mathe42]

Summary by CodeRabbit

• Documentation
  • Added a Compatibility section to the README specifying a minimum Vite version requirement (vite >= 5).

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e582e4 and c1ce285.

📒 Files selected for processing (1)

• README.md

📜 Recent review details

🔇 Additional comments (1)

README.md (1)

9-10: Nice doc fix — compatibility note is now clear and correctly placed.

This resolves the earlier placeholder-heading concern and makes the requirement explicit.

---

📝 Walkthrough

Walkthrough

README.md updated to add a Compatibility section noting a requirement of vite >= 5; no code or public API changes.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Inserted a new "Compatibility" section and added the line indicating vite >= 5 is required; no code or logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 I nibbled a line in the README today,
A "Compatibility" sign to guide the way,
vite ≥ 5 now gleams so bright,
One tiny change, hopped in just right.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update README.md' is too vague and generic; it describes the action (updating a file) rather than the substantive change (adding Vite >=5 compatibility requirement).	Consider a more descriptive title such as 'Add Vite >=5 compatibility requirement to README' to clarify the actual content change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch mathe42-patch-1

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 9-10: Replace the placeholder heading "TESTING" with a meaningful
compatibility heading (e.g., "## Compatibility") and keep the existing
requirement line "This plugin requires vite >=5" directly beneath it; update the
README heading text and ensure the Vite requirement remains as a single bullet
or short paragraph under the new "Compatibility" heading to improve clarity.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fdb3128 and 3e582e4.

📒 Files selected for processing (1)

• README.md