Nx
Enterprise
Nx
fix(vitest): align atomized spec discovery with Vitest's config resolution The glob-based atomized test discovery resolved specs differently from how Vitest resolves them at run time, so the `${ciTargetName}--*` targets could enumerate the wrong spec set with no warning. Two divergences: - The serve config was resolved under Vite `mode: 'development'`, but Vitest runs under `mode: 'test'`. A config that branches `test.include`/`exclude` on `mode` enumerated a different set during graph creation than at test time. Resolve under `mode: 'test'` to match. - `test.includeSource` was globbed even under `typecheck.enabled` + `typecheck.only`, where Vitest collects only type tests and skips in-source files. Gate the includeSource glob with the same `typecheck.only` guard the regular include already uses. The e2e exercises the mode branch via a config that keys `test.include` on `mode`; a unit test covers the typecheck.only + includeSource combination.
nx-cloud record -- nx format:check
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx-cloud record -- nx format:check
Click to copy
Linux
4 CPU cores
67fa98c2
36339