-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Labels
outdatedpriority: mediumMedium Priority (not high, not low priority)Medium Priority (not high, not low priority)scope: bundlersIssues related to webpack, rollupIssues related to webpack, rolluptype: bug
Description
Current Behavior
Vitest deprecated vitest.workspace file, and now propose to use projects field in the top vitest.config file.
So with current approach Nx Plugin treats that there's a test target in the root project and calls it, which results in re-running the whole test suite w/o Nx cache. This is not optimal.
Expected Behavior
Nx plugin ignores root vitest config when he see the projects field
GitHub Repo
No response
Steps to Reproduce
- Create a Mono-repo with Vitest
- Create separate vitest.config files for each project in mono-repo
- Create a root vitest.config file for IDE integration which has
projectsfield - Check the graph and observe that there's a test target on the root project
Nx Report
Node : 22.14.0
OS : darwin-arm64
Native Target : aarch64-macos
yarn : 4.7.0
nx (global) : 21.0.3
nx : 21.4.0
@nx/js : 21.4.0
@nx/jest : 21.4.0
@nx/eslint : 21.4.0
@nx/workspace : 21.4.0
@nx/cypress : 21.4.0
@nx/devkit : 21.4.0
@nx/eslint-plugin : 21.4.0
@nx/plugin : 21.4.0
@nx/storybook : 21.4.0
@nx/vite : 21.4.0
typescript : 5.9.2
---------------------------------------
Registered Plugins:
@nx/eslint/plugin
@nx/vite/plugin
---------------------------------------
Cache Usage: 279.20 MB / 46.04 GBFailure Logs
Package Manager Version
No response
Operating System
- macOS
- Linux
- Windows
- Other (Please specify)
Additional Information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
outdatedpriority: mediumMedium Priority (not high, not low priority)Medium Priority (not high, not low priority)scope: bundlersIssues related to webpack, rollupIssues related to webpack, rolluptype: bug