Allow configuration extending from a library instead of only a relative path

[bradleysmagacz]

Description

We have a large monorepo with biome config files at various levels. With the entire monorepo open in VSCode, the extends functionality works great as we can give it a relative path to the root biome config. However when opening up an individual directory inside of VSCode, this directory can no longer find the root config that it extends from and ends up falling back to biome's default rules.

Ideally we could give it a library path to extend from so we can create a shared library that holds different config files for frontend and backend.

Is this by design or is this something that is on the roadmap to be implemented at some point? I'm happy to contribute to this as well.

[ematipico]

The reason why the feature works as it is now is because Biome doesn't have the infrastructure to resolve libraries yet.

So it was a deliberate choice driven by the infrastructure we have.

We really want to apply the functionality you suggested, but we need to develop the infrastructure to resolve libraries.

I did some initial work a few days ago. We are aware of the fact that we need this functionality for a lot of other stuff. Stay tuned :)

If you'd like to help, you can jump to discord server and start a discussion

[bradleysmagacz]

thanks for the response @ematipico ! I meant to get into the discord, but had conflicting priorities. curious to know if you have any status updates here 😄

[ematipico]

This work will be part of our roadmap that I am writing, we will be publish it in next few weeks

[ftzi]

Excited about it!

[kevinwolfcr]

@bradleysmagacz this was included in the latest nightly release 🎉 , so it might be released in 1.6.0.

[bradleysmagacz]

@kevinwolfcr awesome, thank you! I'm having some trouble getting this to work. Is it designed to be compatible with yarn workspaces? I can see the package in my node_modules folder, I'm exporting the way the documentation describes, but no luck.

If I provide a direct path to where the config file lives that seems to work, but using the associated workspace name and export it does not.

[ematipico]

Are you using yarn PnP?

[bradleysmagacz]

see reply below @kevinwolfcr . I was mistaken it actually is loading it correctly, it just doesn't show any of the errors in my IDE (VS Code) or do any of the auto formatting like if I extend directly from the file path. perhaps this is just an issue with the VSCode extension that needs to be updated?

[Sec-ant]

There's an issue about it, see https://github.com/biomejs/biome-vscode/issues/167 I would suggest that you add a comment there. This might be a LSP client (VSCode Extension) or a server (Biome) thing.

[kevinwolfcr]

I haven't tested it with yarn, I use bun, but if the package is there, it should work.

Can you run biome rage and share its output?

[bradleysmagacz]

okay interesting, it appears to find the config correctly; it just doesn't show anything in VSCode. perhaps the extension needs to be updated?

also, running biome check doesn't seem to emit any of the linter errors, only the formatting errors. running yarn lint does show the lint errors though.

CLI:
  Version:                      1.6.1
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v16.19.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/3.4.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

[kevinwolfcr]

Oh, that's an issue in the Biome's LSP. See #2159