Environment information
CLI:
Version: 1.9.4
Color support: true
Platform:
CPU Architecture: aarch64
OS: macos
Environment:
BIOME_LOG_PATH: unset
BIOME_LOG_PREFIX_NAME: unset
BIOME_CONFIG_PATH: unset
NO_COLOR: unset
TERM: "xterm-256color"
JS_RUNTIME_VERSION: "v18.17.1"
JS_RUNTIME_NAME: "node"
NODE_PACKAGE_MANAGER: "npm/9.6.7"
Biome Configuration:
Status: Loaded successfully
Formatter disabled: false
Linter disabled: false
Organize imports disabled: false
VCS disabled: false
Workspace:
Open Documents: 0
What happened?
git checkout mainecho "const a=1" > test.tsgit commit -m "1"git checkout -b testecho "const a=2" > test.tsgit commit -m "2"mv test.ts test2.tsnpx biome check --changed
test.ts internalError/io INTERNAL ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ No such file or directory (os error 2)
⚠ This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.
Expected result
Should not show an error
I get that --changed is supposed to be used in CI, but it can also be useful locally, e.g. for precommit checks. Probably it should treat uncommited local changes the same way as commits
Code of Conduct
Environment information
What happened?
git checkout mainecho "const a=1" > test.tsgit commit -m "1"git checkout -b testecho "const a=2" > test.tsgit commit -m "2"mv test.ts test2.tsnpx biome check --changedExpected result
Should not show an error
I get that
--changedis supposed to be used in CI, but it can also be useful locally, e.g. for precommit checks. Probably it should treat uncommited local changes the same way as commitsCode of Conduct