extension often stops working on particular files (stale cache?)

[gadicc]

VS Code version

1.104.1

Extension version

3.2.0

Biome version

2.2.3

Operating system

• Windows
• macOS
• Linux

Description

I have this weird but frequent problem where often, vscode biome extension just stops working on some files.

1. No linting info, formatting doesn't work / happen (but no errors anywhere).
2. Restarting vscode, clearing cache, nothing seems to help.
3. However, if I create a new file and copy the contents over, that works. Then I ran rename the file back to the original.
4. The CLI always works.

I was able to fix the issue by:

1. Closing vscode
2. Killing any still running servers
3. rm -rf .cache/biome
4. Restart vscode
5. Close / re-open the affected file, and biome was working again.

I'll report back on anything else I notice but mostly wanted to post this in case it helps others.

Steps to reproduce

Unfortunately, I don't know how to cause / reproduce this. Beyond editing a file for a long time perhaps, at some point it just stops working, and then never works for that filename again.

Expected behavior

Should continue working for any file.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

Logs

[evanmoelter]

My team and I have also been experiencing this issue sporadically. I'm on MacOS 15.6 (w/ an M1 Pro) and Cursor 1.6.45 (VSCode 1.99.3). Anecdotally, I've only noticed it happening with .tsx files.

Unfortunately I don't have much else to add to help with narrowing down the issue. Happy to help test any fixes though.