fix: Correct path resolution for .vite-port file in ClineProvider #4007
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This PR fixes the issue where ClineProvider was looking for the .vite-port file in the wrong location, causing it to always fall back to the default port.
When multiple development servers are launched in different repositories, each Vite server uses a different port:
Without correctly reading the .vite-port file, the application cannot connect to the right Vite server instance.
Implementation
Updated the path resolution in ClineProvider.ts to correctly point to the project root where the Vite development server creates the .vite-port file.
How to Test
Fixes #4006
Important
Fixes path resolution for
.vite-port
file inClineProvider.ts
to ensure correct Vite server connection..vite-port
file inClineProvider.ts
to correctly point to the project root..vite-port
file.This description was created by
for cb246ee. You can customize this summary. It will automatically update as commits are pushed.