fix(core): fix vitest test runner options for angular in cnw #33921
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit e6a30e5
☁️ Nx Cloud last updated this comment at |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: leosvelperez <leosvelperez@users.noreply.github.com>
nx-cloud
bot
requested review from
a team,
meeroslav and
vsavkin
as code owners
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
Nx Cloud has identified a possible root cause for your failed CI:
Our PR modifies Angular/Vitest workspace creation options, while the failing e2e-maven tests call the Spring Initializr API which recently changed validation rules to reject Spring Boot 3.4.0 (requiring >=3.5.0). This is an external service change unrelated to our PR changes, affecting pre-existing hardcoded version configuration in the Maven test utilities.
No code changes were suggested for this issue.
If the issue was transient, you can trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
## Current Behavior Creating a new Angular workspace with Vitest results in no test setup being generated. This happens because the `vitest` option is no longer available, and instead, there are two options: `vitest-angular` and `vitest-analog`. ## Expected Behavior Creating a new Angular workspace should prompt for Vitest with Angular or Vitest with Analog to set up the tests. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: leosvelperez <leosvelperez@users.noreply.github.com> Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
Current Behavior
Creating a new Angular workspace with Vitest results in no test setup being generated. This happens because the
vitestoption is no longer available, and instead, there are two options:vitest-angularandvitest-analog.Expected Behavior
Creating a new Angular workspace should prompt for Vitest with Angular or Vitest with Analog to set up the tests.