Environment information
CLI:
Version: 2.1.2
Color support: true
Platform:
CPU Architecture: aarch64
OS: macos
Environment:
BIOME_LOG_PATH: unset
BIOME_LOG_PREFIX_NAME: unset
BIOME_CONFIG_PATH: unset
BIOME_THREADS: unset
NO_COLOR: unset
TERM: xterm-ghostty
JS_RUNTIME_VERSION: v24.6.0
JS_RUNTIME_NAME: node
NODE_PACKAGE_MANAGER: unset
Biome Configuration:
Status: Not set
Path: unset
Workspace:
Open Documents: 0
What happened?
I was doing some digging to figure out why my Mac was running out of storage space, then I discovered that my ~/Libary/Caches/dev.biomejs.biome/biome-logs directory contained 162 GB of logs. I'm assuming this is safe to delete, but it would be great if there was some way of... not having this.
It's worth noting that I use the Biome extension in Zed, and I had a JSON file open that was being constantly updated, but logs from a single hour were 125GB. This shouldn't really be allowed to happen.
Expected result
Logs should be rotated/deleted.
Code of Conduct
Environment information
What happened?
I was doing some digging to figure out why my Mac was running out of storage space, then I discovered that my
~/Libary/Caches/dev.biomejs.biome/biome-logsdirectory contained 162 GB of logs. I'm assuming this is safe to delete, but it would be great if there was some way of... not having this.It's worth noting that I use the Biome extension in Zed, and I had a JSON file open that was being constantly updated, but logs from a single hour were 125GB. This shouldn't really be allowed to happen.
Expected result
Logs should be rotated/deleted.
Code of Conduct