-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
🐛 Biome Linting Runs in Projects Without Configuration or Dependency When VSCode Extension is Enabled #330
Comments
I have the same problem, sometimes I open a project that uses ESLint or other linter but Biome keeps showing errors and as there is no biome configuration it shows all recomended errors |
Switching to the pre-release version solves this issue for me. (Please refer to biomejs/biome#1630) Hope the support of multi-folder workspaces to be released soon! |
I think this will be resolved by the pre-release of v3, could you try that? Set true to the |
There is still an issue i am facing when there is an biome extension installed but no biome json file is there in the repo, still the biome is showing those as errors. I dont want it as in this repo i have already prettier and eslint configured. I am using biome extension version 1.9.2 |
@kotasudhakar did you follow the conversation? Did you try the pre-release with the new extension configuration? If so, then please create a reproduction and open a new issue |
I was looking for a solution to this same issue and tried the latest pre-release ( See #375 for details. |
VS Code version
1.92.2
Extension version
2.3.0
Biome version
1.8.3
Operating system
Description
The Biome linter runs on projects where it is not configured or installed. Specifically, Biome executes linting even when:
package.json
does not include a Biome dependency.biome.json
or any other configuration file related to Biome in the project.Steps to reproduce
package.json
.biome.json
or similar configuration in the project.Expected behavior
Biome should not run linting in projects unless explicitly installed or configured within the project settings or dependency files.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Link to a minimal reproduction
No response
Logs
No response
The text was updated successfully, but these errors were encountered: