dev: dynamic Vite port detection for webview development

[KJ7LNW]

Context

This PR implements a solution for the Vite port collision issue that allows easier development of Roo across multiple instances of VSCode in different Roo repository directories.

This may also fix crashes and strange behavior between multiple running instances that would otherwise create port conflicts.

Implementation

The solution uses a fully automated process:

• When Vite automatically selects an alternative port, a custom plugin automatically writes the port to a '.vite-port' file in the repository root
• ClineProvider automatically reads the port from this file, falling back gracefully to port 5173 if the file doesn't exist
• No user intervention is necessary as the entire process is handled automatically
• Added detailed logging for debugging
• Added .vite-port to .gitignore

How to Test

1. Run multiple instances of VSCode with different Roo repositories
2. Press F5 in each instance to run Roo in the VS Code extension development host
3. Verify that each instance connects to its own Vite server, even when they use different ports

Get in Touch

Discord: KJ7LNW

---

Important

Implements dynamic Vite port detection to avoid port collisions by writing and reading the port from a .vite-port file, with changes in ClineProvider.ts and vite.config.ts.

• Behavior:
  • Implements dynamic Vite port detection to avoid port collisions in ClineProvider.ts and vite.config.ts.
  • Writes selected Vite port to .vite-port file using a custom plugin in vite.config.ts.
  • Reads Vite port from .vite-port file in getHMRHtmlContent() in ClineProvider.ts, defaults to 5173 if file is missing.
• Logging:
  • Adds logging for port usage and errors in both ClineProvider.ts and vite.config.ts.
• Misc:
  • Adds .vite-port to .gitignore.

^{This description was created by for 0a3ba71. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a3ba71

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mrubens]

Thank you!