fix: resolve the vitest path alias to a native filesystem path - #69
Merged
arnabnandy7 merged 1 commit intoAug 31, 2026
Merged
Conversation
new URL(...).pathname returns "/C:/Users/.../src" on Windows, which is not a valid filesystem path, so every test file failed to resolve its "@/..." imports and the suite could not run. fileURLToPath returns a correct native path on all platforms and leaves POSIX behavior unchanged. Signed-off-by: AyanAta42 <[email protected]>
Owner
|
LGTM, thanks for your contribution. |
arnabnandy7
approved these changes
Aug 31, 2026
github-project-automation
Bot
moved this from In Progress
to Completed
in Open issue portal development
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I set the project up on Windows, installed Node 24 according to the README's requirement, ran npm ci, then npm test — and every test file failed to resolve its @/... imports. New URL(...).pathname returns "/C:/Users/.../src" on Windows, which is not a valid filesystem path, so every test file failed to resolve its "@/..." imports and the suite could not run. fileURLToPath returns a correct native path on all platforms and leaves POSIX behavior unchanged.