Configuration file not found – biome.json configuration resolution

Configuration file not found – biome.json configuration resolution

Goal: Clarify whether a .biomeignore file at the repository root takes precedence over the files.ignore array defined in a biome.json configuration when both are present, particularly in setups with nested biome.json files in a monorepo.

Constraints: Biome’s configuration lookup walks upward from the current working directory to locate biome.json, biome.jsonc or biome.json5, falling back to defaults if none is found. The exact search order and how multiple config layers combine are version‑sensitive, and the documentation does not explicitly state the evaluation order between .biomeignore and files.ignore, leading to ambiguous effective ignore sets when configs are stacked.

Questions: Does .biomeignore override files.ignore defined in a deeper biome.json? How does the effective ignore set change when biome is invoked from a subdirectory versus the workspace root? Is there a defined order of evaluation for these ignore sources across config hierarchy?