Skip to content
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

🐛 Allow workspace-relative paths for biome.lsp.bin #420

Open
1 of 3 tasks
cr7pt0gr4ph7 opened this issue Nov 7, 2024 · 2 comments
Open
1 of 3 tasks

🐛 Allow workspace-relative paths for biome.lsp.bin #420

cr7pt0gr4ph7 opened this issue Nov 7, 2024 · 2 comments
Labels
Bug confirmed Report has been confirmed as a valid bug Good first issue Help wanted External contributions are welcome v3-prerelease

Comments

@cr7pt0gr4ph7
Copy link

cr7pt0gr4ph7 commented Nov 7, 2024

VS Code version

1.93.1

Extension version

2024.10.131712

Biome version

1.9.4

Operating system

  • Windows
  • macOS
  • Linux

Description

The old biome.lspBin setting in 2.3.x supported workspace-relative paths, while Biome 3.x (both for the new biome.lsp.bin setting and for the old biome.lspBin setting) only supports absolute paths.

Steps to reproduce

// <workspace>/.vscode/settings.json
{
  "biome.lsp.bin": "app/node_modules/.bin/biome"
}
// <workspace>/app/package.json
{
  "devDependencies": {
    "@biomejs/biome": "1.9.4"
  },
  "type": "module"
}

Expected behavior

There should be a package-manager-independent way to reference a workspace-relative biome installation, either by supporting relative paths like app/node_modules/.bin/biome (as it was implemented in 2.x) or by allowing the use of placeholders as in ${workspaceFolder}/app/node_modules/.bin/biome.

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

Logs

2024-11-07 15:11:12.984 [info] 
...
2024-11-07 15:11:12.984 [info] Biome extension 2024.10.131712 activated
2024-11-07 15:11:16.690 [error] Could not find the Biome binary
@nhedger
Copy link
Member

nhedger commented Nov 7, 2024

Thanks for opening this issue, I agree with you.

I'd accept a PR for this if you're up to the challenge, otherwise, we'll somehow get it done before releasing the stable version.

@nhedger nhedger added Bug confirmed Report has been confirmed as a valid bug Help wanted External contributions are welcome Good first issue v3-prerelease and removed Triage labels Nov 7, 2024
@AshutoshNanaware
Copy link
Contributor

AshutoshNanaware commented Nov 18, 2024

Hey , I will look into this and try fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug confirmed Report has been confirmed as a valid bug Good first issue Help wanted External contributions are welcome v3-prerelease
Projects
None yet
Development

No branches or pull requests

3 participants