Thanks to visit codestin.com
Credit goes to github.com

Skip to content

πŸ› extends is not able to resolve configuration file in monorepo when child config is two levels deepΒ #7343

@chrisgrieser

Description

@chrisgrieser

Environment information

CLI:
  Version:                      2.2.2
  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.6.0
  JS_RUNTIME_NAME:              node
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       Loaded successfully
  Path:                         /Users/chrisgrieser/.config/biome.jsonc
  Formatter enabled:            true
  Linter enabled:               true
  Assist enabled:               true
  VCS enabled:                  false

Workspace:
  Open Documents:               0

What happened?

I have a monorepo, with two biome configs:

~/.config/biome.jsonc
~/.config/obsidian/vimrc/biome.jsonc

The second one has the following content:

{
	"root": false,
	"extends": ["../../biome.jsonc"],
}

However, the child config is ignored, and running biome check . in the ~/.config/obsidian/vimrc results in this error, even though the biome.jsonc in the repo root exists and is a valid biome configuration working elsewhere in the monorepo (where there is no child config)

> biome check .
configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  βœ– Failed to resolve the configuration from ../../biome.jsonc

    Caused by:
      Could not resolve ../../biome.jsonc: module not found


configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  βœ– Biome exited because the configuration resulted in errors. Please fix them.

This is pretty much the issue described in #6483, which was said to be fixed in biome 2.1, but still exists for me.

repro-repo: https://github.com/chrisgrieser/biome-repro-1756309977877

Expected result

child configuration should work.

Code of Conduct

  • I agree to follow Biome's Code of Conduct

Metadata

Metadata

Assignees

Labels

A-CoreArea: coreA-ProjectArea: projectS-Bug-confirmedStatus: report has been confirmed as a valid bug

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions