feat(testing): move test config more into nx.json targetDefaults #19963
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.
Current Behavior
jest
targets have a lot of the same options added to them inproject.json
test
target defaults are all added tonx.json
defaults undertest
which leads to some weird cases when bothvitest
andjest
are used whenjest.preset.js
will be an input forvitest
tasks.Expected Behavior
Common
jest
options are added tonx.json
undertargetDefaults
so the options are not added toproject.json
.Target defaults for test executors are added under the executor so
@nx/jest:jest
settings are separate from@nx/vite:vitest
settings.Related Issue(s)
Fixes #