refactor(@angular/build): add option to dump unit test build output #31222
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.
Debugging the
unit-test
builder can be challenging, particularly when using runners like Vitest that rely on virtual or in-memory files for test setup and execution. It is difficult to inspect the final build artifacts that are passed to the test runner.This commit introduces a new hidden boolean option,
dumpVirtualFiles
, to theunit-test
builder's schema. When this option is enabled, the builder will write the full build output to a directory within the project's cache (.angular/cache/<project-name>/unit-test/output-files/
).This provides a crucial debugging mechanism, allowing developers to inspect the exact contents of the files being used in the test execution, which helps in troubleshooting complex configuration and build-related problems.