-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vitest workspace - config from packages leaking into other packages #5541
Comments
Does this happen with |
Just tested, it appears to be happening in both |
@seanogdev I tested with Btw, where is this file supposed to be generated? Is it at root or at Also this might be partially a plugin side issue with current Vitest workspace's limitation #5277 (comment) since it looks like It looks like the plugin supports AutoImport({
imports: ["vue"],
eslintrc: {
enabled: true,
filepath: fileURLToPath(
new URL("../../.eslintrc-auto-import.json", import.meta.url)
),
},
}) |
I started experiencing this issue, with and without It looks like the issue has something to do with the current working directory because: given a directory structure like this:
and AutoImport({
imports: ["vue"],
eslintrc: {
enabled: true,
filepath: ".eslintrc-auto-import.json"
},
}) the
instead of always at the location relative to |
I am seeing an issue where a My workaround is to only apply the
|
Describe the bug
Noticing that when we run vitest in a workspace, there are certain side effects happening.
For example, we have https://github.com/unplugin/unplugin-auto-import installed, this generates an eslint file that gives us a file to generate globals for what is auto importable so eslint doesnt complain.
Noticing that when we run vitest in the root, the generate file gets added to other packages and too the workspace
Reproduction
https://github.com/seanogdev/vitest-workspace-issue
System Info
Used Package Manager
pnpm
Validations
The text was updated successfully, but these errors were encountered: