biome: π [2.0.0-beta.6] `useIgnoreFile` causes Biome not to lint anything at all
Environment information
CLI:
Version: 2.0.0-beta.6
Color support: true
Platform:
CPU Architecture: aarch64
OS: macos
Environment:
BIOME_LOG_PATH: unset
BIOME_LOG_PREFIX_NAME: unset
BIOME_CONFIG_PATH: unset
BIOME_THREADS: unset
NO_COLOR: unset
TERM: xterm-256color
JS_RUNTIME_VERSION: v24.0.2
JS_RUNTIME_NAME: node
NODE_PACKAGE_MANAGER: yarn/4.9.1
Biome Configuration:
Status: Loaded successfully
Path: biome.json
Formatter enabled: true
Linter enabled: true
Assist enabled: true
VCS enabled: true
Workspace:
Open Documents: 0
What happened?
I was using Biome 1.9.0 with the following configuration:
{
"$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
"vcs": {
"enabled": true,
"clientKind": "git",
"useIgnoreFile": true
},
"files": {
"ignore": [".yarn"]
},
// β¦
and this setup resulted in a fair amount of files linted:
% biome lint
Checked 527 files in 552ms. No fixes applied.
Upon updating to 2.0.0-beta.6, and running biome migrate --write this got automatically changed to:
{
"$schema": "https://biomejs.dev/schemas/2.0.0-beta.6/schema.json",
"vcs": {
"enabled": true,
"clientKind": "git",
"useIgnoreFile": true
},
"files": {
"includes": ["**", "!**/.yarn"]
},
// β¦
but this resulted in no files being matched!
% yarn lint
Checked 0 files in 84ms. No fixes applied.
lint βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β No files were processed in the specified paths.
βΉ Check your biome.json or biome.jsonc to ensure the paths are not ignored by the configuration.
βΉ These paths were provided but ignored:
β The list is empty.
Expected result
The number of files linted before upgrade & migrate should match the number of files after doing so.
Code of Conduct
- I agree to follow Biomeβs Code of Conduct
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 16 (10 by maintainers)
Iβll look into it. I definitely fixed this one before, because it was reported a few weeks ago. This is probably a regression of monorepo support, which changed a few things around the architecture. Thing is, there are tests in place, so maybe the issue is somewhere else.
Related: https://github.com/biomejs/biome/issues/6134