You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set up a workspace with roughly 50 workspace packages, but I could not run all tests of the workspace because I ran into the following issue:
Error: Project name "client" is not unique. All projects in a workspace should have unique names.
A big project benefits from having similar structures in different parts of a big monorepo. So it is not surprising that packages with similar purpose end up having the same directory names.
Suggested solution
Why not following rather the same uniqueness restrictions that already exist for package managers and hence will guarantee unique names?
The vitest workspace should identify workspace packages by the "name" property of the package.json.
Additionally: This will also reduce e.g. the nesting level seen in vitest VSCode plugin in the "Testing" panel.
You can add a name property to the config. I don't know if we can use package.json to get the name since workspace file supports any folder, not just packages.
Clear and concise description of the problem
I set up a workspace with roughly 50 workspace packages, but I could not run all tests of the workspace because I ran into the following issue:
A big project benefits from having similar structures in different parts of a big monorepo. So it is not surprising that packages with similar purpose end up having the same directory names.
Suggested solution
Why not following rather the same uniqueness restrictions that already exist for package managers and hence will guarantee unique names?
The vitest workspace should identify workspace packages by the "name" property of the
package.json
.Additionally: This will also reduce e.g. the nesting level seen in vitest VSCode plugin in the "Testing" panel.
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: