-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
feat: workspaceIssues and PRs related to the workspace featureIssues and PRs related to the workspace featurep4-importantViolate documented behavior or significantly improves performance (priority)Violate documented behavior or significantly improves performance (priority)
Description
Describe the bug
I've got a monorepo with a few packages in it. In one of those packages, I need to use two different testing setups (it's an electron app so there's both main process and renderer process setups required).
When running the tests through vitest's workspace feature, I've noticed that it gathers all the config files listed in the vitest.workspace.js file, but only uses the first config file for a given package. I've made a minimal repo here
@sheremet-va has helpfully provided a workaround to this issue. You can just put the other config file in a different folder, then adjust your includes
as appropriate. Example here.
Reproduction
https://github.com/conallroli/vitest-workspace-repro
System Info
System:
OS: macOS 13.2
CPU: (10) arm64 Apple M1 Pro
Memory: 65.48 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
Yarn: 4.1.1 - ~/.nvm/versions/node/v20.11.1/bin/yarn
npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
Browsers:
Chrome: 123.0.6312.122
Safari: 16.3
npmPackages:
vitest: ^1.5.0 => 1.5.0
Used Package Manager
yarn
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
douglasg14b, tommoyang, amitz and tamasfabi
Metadata
Metadata
Assignees
Labels
feat: workspaceIssues and PRs related to the workspace featureIssues and PRs related to the workspace featurep4-importantViolate documented behavior or significantly improves performance (priority)Violate documented behavior or significantly improves performance (priority)