fix(@angular/build): normalize setupFiles paths to POSIX for vitest runner - #33831
Open
alan-agius4 wants to merge 1 commit into
Open
fix(@angular/build): normalize setupFiles paths to POSIX for vitest runner#33831alan-agius4 wants to merge 1 commit into
alan-agius4 wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the unit-test builder options to convert setup file paths to POSIX format using toPosixPath. Additionally, it simplifies boolean checks in the SSR response utility by removing redundant Boolean() wrappers. There are no review comments, and we have no feedback to provide.
alan-agius4
added
action: review
alan-agius4
force-pushed
the
fix/vitest-windows-setup-files
branch
from
August 11, 2026 08:30
0db3d21 to
11fb576
Compare
…unner On Windows, absolute paths generated by joining the workspace root and the configured setup files contain backslashes. This causes a mismatch during test execution when the Vitest in-memory loading plugin resolves paths in POSIX format (with forward slashes) and attempts to look them up in the entry point mapping, leading to failed import resolutions. Normalizing `setupFiles` paths to POSIX at the options normalization stage ensures consistency across the entire build and execution pipeline, resolving the import resolution errors on Windows. Closes angular#33749
alan-agius4
force-pushed
the
fix/vitest-windows-setup-files
branch
from
August 11, 2026 08:30
11fb576 to
93e1f5b
Compare
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
1 participant
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.
On Windows, absolute paths generated by joining the workspace root and the configured setup files contain backslashes. This causes a mismatch during test execution when the Vitest in-memory loading plugin resolves paths in POSIX format (with forward slashes) and attempts to look them up in the entry point mapping, leading to failed import resolutions.
Normalizing
setupFilespaths to POSIX at the options normalization stage ensures consistency across the entire build and execution pipeline, resolving the import resolution errors on Windows.Closes #33749