Skip to content

fix(@angular/build): provide vitest globals in unit-test builder #30297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 13, 2025

Conversation

clydin
Copy link
Member

@clydin clydin commented May 13, 2025

The experimental unit-test builder with the vitest runner now provides the test APIs also as globals. This increases the potential compatibility for existing karma/jasmine based tests. The initial unit tests within a newly generated application, for instance, now require no changes to execute with the new builder.

The experimental `unit-test` builder with the `vitest` runner now provides
the test APIs also as globals. This increases the potential compatibility
for existing karma/jasmine based tests. The initial unit tests within a
newly generated application, for instance, now require no changes to
execute with the new builder.
@clydin clydin added the target: rc This PR is targeted for the next release-candidate label May 13, 2025
@clydin clydin requested a review from alan-agius4 May 13, 2025 17:00
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label May 13, 2025
@clydin clydin merged commit 7b8c9af into angular:main May 13, 2025
33 checks passed
@clydin
Copy link
Member Author

clydin commented May 13, 2025

The changes were merged into the following branches: main, 20.0.x

@clydin clydin deleted the unit-test/vitest-globals branch May 13, 2025 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: @angular/build target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants