🐞 Bug: Fix npm install failing due to Vuetify dependency conflict

[naman79820]

Fixes #776

Describe the changes you have made in this PR -

This PR fixes an npm install failure caused by incompatible peer dependencies between vuetify and vite-plugin-vuetify.

The project was using mismatched pre-release versions, which resulted in an ERESOLVE error when running npm install on a clean setup.
This change aligns both packages to compatible versions so that dependency installation works without requiring --legacy-peer-deps or --force.

With a fresh clone, npm install works because package-lock.json already contains a working dependency setup.
When node_modules and package-lock.json are removed, npm has to resolve everything again, which leads to peer dependency conflicts with the current dependency stack.
Keeping the lockfile avoids this and ensures consistent installs until the dependencies are upgraded.

Only dependency versions were updated; no application logic or UI behavior was changed.

Screenshots of the UI changes (If any) -

---

Code Understanding and AI Usage

Did you use AI assistance (ChatGPT, Claude, Copilot, etc.) to write any part of this code?

• No, I wrote all the code myself
• Yes, I used AI assistance (continue below)

If you used AI assistance:

• I have reviewed every single line of the AI-generated code
• I can explain the purpose and logic of each function/component I added
• I have tested edge cases and understand how the code handles them
• I have modified the AI output to follow this project's coding standards and conventions

Explain your implementation approach:

---

Checklist before requesting a review

• I have added proper PR title and linked to the issue
• I have performed a self-review of my code
• I can explain the purpose of every function, class, and logic block I added
• I understand why my changes work and have tested them thoroughly
• I have considered potential edge cases and how my code handles them
• If it is a core feature, I have added thorough tests
• My code follows the project's style guidelines and conventions

---

Note: Please check Allow edits from maintainers if you would like us to assist in the PR.

Summary by CodeRabbit

• Chores
  • Updated key project dependencies (UI framework and build tooling) to newer patch/minor releases for improved stability, compatibility, and build reliability. These dependency updates focus on keeping the UI toolkit and build plugins current to reduce integration issues and support smoother local builds and deployments.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	a7772af
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/6991ed33fdbc2c000882648e
😎 Deploy Preview	https://deploy-preview-779--circuitverse.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 36 (🔴 down 12 from production) Accessibility: 66 (🔴 down 7 from production) Best Practices: 92 (no change from production) SEO: 82 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

This pull request updates two dependencies in package.json: vuetify from ^3.0.0-beta.0 to ~3.0.5, and vite-plugin-vuetify from ^1.0.0-alpha.0 to ~1.0.2. No other code changes were made. These version changes modify only dependency declarations and do not introduce new exported or public entities.

🚥 Pre-merge checks | ✅ 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: fixing npm install failure caused by Vuetify dependency conflict, which matches the package.json version updates.
Linked Issues check	✅ Passed	The PR successfully resolves issue #776 by updating vuetify and vite-plugin-vuetify to compatible versions, eliminating the ERESOLVE peer dependency conflict and enabling npm install without --legacy-peer-deps.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to resolving the dependency conflict; only package.json versions were updated with no application logic or UI changes introduced.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ 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

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[naman79820]

@tachyons @ThatDeparted2061
ready to be reviewed.

[naman79820]

@Nihal4777

[naman79820]

@tachyons @Nihal4777

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@package.json`:
- Line 44: Update package.json dependency pins for vuetify and
vite-plugin-vuetify to stable, range-enabled versions instead of exact,
old/pre-release pins: replace "vuetify": "3.0.5" with a stable 3.x reference
that allows patch updates (e.g. "~3.11.8" or "^3.11.8") and replace
"vite-plugin-vuetify": "1.0.0-alpha.12" with a stable release (e.g. "~1.0.2" or,
if you want the newer major, "^2.1.3"); use ~ if you want to allow only patch
updates, or ^ for minor+patch, then reinstall and re-run dependency audit/fix to
verify vulnerabilities are resolved.