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

🐛 Extension does not work when using shared config from module #2159

Closed
1 of 3 tasks
kevinwolfcr opened this issue Mar 12, 2024 · 1 comment · Fixed by #2160
Closed
1 of 3 tasks

🐛 Extension does not work when using shared config from module #2159

kevinwolfcr opened this issue Mar 12, 2024 · 1 comment · Fixed by #2160
Assignees

Comments

@kevinwolfcr
Copy link
Contributor

kevinwolfcr commented Mar 12, 2024

VS Code version

1.87.1

Extension version

2.2.2

Biome version

1.6.0

Operating system

  • Windows
  • macOS
  • Linux

Description

After extending a configuration resolved from a node module, the extension stopped working, it says the Biome version on the status bar, but neither the linter nor the formatter are working.

Steps to reproduce

  1. Install a shareable configuration from npm (you can use mine)
  2. Extend the configuration on biome.json (see snippet below)
{
  "$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
  "extends": ["@kevinwolfcr/biome-config"],
}

Expected behavior

Same behavior as extending a config using its path.

Does this issue occur when using the CLI directly?

No

Logs

No logs are shown at all
@Sec-ant Sec-ant transferred this issue from biomejs/biome-vscode Mar 22, 2024
@Sec-ant Sec-ant self-assigned this Mar 22, 2024
@Sec-ant
Copy link
Member

Sec-ant commented Mar 22, 2024

I transferred this issue because this is a bug in biome_lsp and biome_fs. A fix will be pushed soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants