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

[daniele-orlando]

Environment information

Details

biome rage

CLI:
Version: 2.4.4
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.0
JS_RUNTIME_NAME: node
NODE_PACKAGE_MANAGER: unset

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 biome lint file.ts

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:
0: __mh_execute_header
1: __mh_execute_header
2: __mh_execute_header
... (omitted for clarity, it's __mh_execute_header repeated)
25: __mh_execute_header
26: __mh_execute_header
27: __mh_execute_header
28: __pthread_cond_wait

file.ts 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.

Checked 0 files in 6ms. No fixes applied.
lint ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✖ No files were processed in the specified paths.

ℹ Check your biome.json or biome.jsonc to ensure the paths are not ignored by the configuration.

ℹ These paths were provided but ignored:

• file.ts

Expected result

It should not fail.

Reproduction

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

Code of Conduct

• I agree to follow Biome's Code of Conduct

[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.

[ematipico]

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:

[daniele-orlando]

Sure, I have updated the issue description with a reproduction code.

[daniele-orlando]

Doing some debugging, I found that this is the rule that raises the error.

"linter": {
  "rules": {
    "nursery": {
      "noParametersOnlyUsedInRecursion": {"level": "error"}, // [JavaScript]
    },
  },
}

Rewriting it to this does not raise the error.

"linter": {
  "rules": {
    "nursery": {
      "noParametersOnlyUsedInRecursion": "error", // [JavaScript]
    },
  },
}

Rewriting it to this does not raise the error too.

"linter": {
  "rules": {
    "nursery": {
      "noParametersOnlyUsedInRecursion": {"level": "off"}, // [JavaScript]
    },
  },
}

[daniele-orlando]

Hi dear @ematipico, thanks for your effort on working on the issue. Unfortunately I need to report that the error still persists in last version 2.4.5. I opened the issue #9314 with the reproduction details.