VS Code version

1.90.1

Extension version

2.3.0

Biome version

1.8.1

Operating system

• Windows
• macOS
• Linux

Description

Files that have been opened before modifying biome.json will be affected by the modified configuration, but the linter will be restored after closing and reopening.

Running biome check from the local command line, biome works fine.

Screenshots:

Before saving config file:

Immediately after saving config file:

Reopen the target file:

Steps to reproduce

1. Init the config file with biome init.
2. Modify the config file.
3. Open a new file tab in vscode.

Expected behavior

In theory, biome should be able to read local configuration files.

Does this issue occur when using the CLI directly?

No

Logs

No output is found.