refactor(@angular/build): use in-memory provider for Vitest runner #31116
+170
−85
Conversation
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
The Vitest unit-test runner is updated to use a fully in-memory provider for test files and build artifacts. Previously, the runner would write bundled test files to a temporary directory on disk. This exposed intermediate build artifacts to the user in test output and incurred an unnecessary performance penalty from disk I/O. With this change, a custom Vite plugin now serves all test-related files (including test entry points, code chunks, and polyfills) directly from the in-memory build results. This provides two key benefits: 1. **Improved Developer Experience**: Vitest now operates on the original TypeScript source file paths. This ensures that test output, error messages, and stack traces correctly reference the files authored by the developer, simplifying debugging. 2. **Increased Performance**: By eliminating all disk writes and the need for a temporary output directory, the test setup is faster and more efficient, especially in watch mode.
The unit test suite for the `exclude` option in the Vitest runner was previously disabled. This change re-enables the test suite to confirm that the `exclude` option is functioning correctly and preventing specified test files from being executed.
clydin
added
the
action: review
jkrems
approved these changes
Sep 4, 2025
clydin
added
action: merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Vitest unit-test runner is updated to use a fully in-memory provider for test files and build artifacts. Previously, the runner would write bundled test files to a temporary directory on disk. This exposed intermediate build artifacts to the user in test output and incurred an unnecessary performance penalty from disk I/O.
With this change, a custom Vite plugin now serves all test-related files (including test entry points, code chunks, and polyfills) directly from the in-memory build results. This provides two key benefits:
Closes #30822
Closes #30823