Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Jan 7, 2026

This addresses issue #31652 where debugging failed to target the correct project instance. When running browser tests, Vitest appends the browser name to the project identifier. This change updates the CLI to match that naming convention when initiating a debug session, ensuring the correct project is selected.

Fixes #31652

…ebugging

This addresses issue angular#31652 where debugging failed to target the correct project instance. When running browser tests, Vitest appends the browser name to the project identifier. This change updates the CLI to match that naming convention when initiating a debug session, ensuring the correct project is selected.

Fixes angular#31652
@clydin clydin added the target: patch This PR is targeted for the next patch release label Jan 7, 2026
@hybrist hybrist added the action: merge The PR is ready for merge by the caretaker label Jan 7, 2026
@clydin clydin merged commit 32adc3a into angular:main Jan 7, 2026
37 checks passed
@clydin
Copy link
Member Author

clydin commented Jan 7, 2026

This PR was merged into the repository. The changes were merged into the following branches:

@clydin clydin deleted the unit-test/vitest-debug-browsers branch January 7, 2026 17:22
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: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unit-test builder with vitest runner and --debug option fails

2 participants