🐛 [v2.4.5] processing panicked: called `Option::unwrap()` on a `None` value

[daniele-orlando]

Environment information

Details

```bash biome rage ```

CLI:
Version: 2.4.5
Color support: true

Platform:
CPU Architecture: aarch64
OS: macos

Environment:
BIOME_LOG_PATH: unset
BIOME_LOG_PREFIX_NAME: unset
BIOME_LOG_LEVEL: unset
BIOME_LOG_KIND: unset
BIOME_CONFIG_PATH: unset
BIOME_THREADS: unset
BIOME_WATCHER_KIND: unset
BIOME_WATCHER_POLLING_INTERVAL: unset
NO_COLOR: unset
TERM: xterm-256color
JS_RUNTIME_VERSION: v25.6.1
JS_RUNTIME_NAME: node
NODE_PACKAGE_MANAGER: npm/11.9.0

Biome Configuration:
Status: Loaded successfully
Path: biome.jsonc
Formatter enabled: true
Linter enabled: true
Assist enabled: true
VCS enabled: true
HTML full support enabled: unset

Workspace:
Open Documents: 0

What happened?

RUST_BACKTRACE=1 npx -p @biomejs/biome@2.4.5 biome check "$Dir"/*

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue.

When opening the issue, please provide a minimal reproduction, or identify and share the file/code that triggers it. Without a way to reproduce the error, the error can't be fixed:

Source Location: /Users/runner/work/biome/biome/crates/biome_analyze/src/options.rs:27:35
Thread Name: biome::workspace_worker_0
Message: called Option::unwrap() on a None value
Stack Trace: Re-run with RUST_BACKTRACE=1 to capture the stack trace

demo.html internalError/panic INTERNAL

✖ processing panicked: called Option::unwrap() on a None value

⚠ This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

Reproduction

1. Download and extract Reproduction 2.zip
2. cd "Reproduction 2"
3. sh ./demo.sh
4. See the world falling apart.

If you are unable to reproduce using previous procedure, try with this:

1. https://codesandbox.io/p/devbox/pzs46p
2. npx -p @biomejs/biome@2.4.5 biome check demo.html demo/

NOTE: this CodeSanbox instance will be deleted after reproduction confirmation from one the maintainers.

Expected result

It should not fail.

Code of Conduct

• I agree to follow Biome's Code of Conduct

[ematipico]

I can't reproduce the issue using your reproduction. Both configurations you provided work.

[github-actions]

Hello @daniele-orlando, please provide a minimal reproduction. You can use one of the following options:

• Provide a link to our playground, if it's applicable.
• Provide a link to GitHub repository. To easily create a reproduction, you can use our interactive CLI via npm create @biomejs/biome-reproduction

Issues marked with S-Needs repro will be closed if they have no activity within 3 days.

[daniele-orlando]

This is what I get when I download the Reproduction 2.zip file and I run sh ./demo.sh.

[daniele-orlando]

@ematipico Is the demo.sh script showing you the linting issues on demo.html and demo/milestone-sdk/Lib/AudioAvailability.js files? If not, it could be that the glob is not expanded on your shell.

To be sure try running

npx -p @biomejs/biome@2.4.5 biome check demo.html demo/

[daniele-orlando]

@ematipico if you are unable to reproduce on your machine, please checkout the CodeSanbox instance I created for this issue.

https://codesandbox.io/p/devbox/pzs46p

npx -p @biomejs/biome@2.4.5 biome check ./demo.html ./demo/

[daniele-orlando]

[ematipico]

Ah, the panic is hidden by the diagnositcs