🐛 Biome encountered an unexpected error

[wojtekmaj]

Environment information

CLI:
  Version:                      1.6.4
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.12.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/4.1.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

npx @biomejs/biome lint . --apply-unsafe resulted with:

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:

Source Location: /Users/runner/work/biome/biome/crates/biome_rowan/src/ast/mod.rs:238:13
Thread Name: biome::worker_0
Message: Tried to cast node with kind JS_EXPRESSION_STATEMENT as `"biome_js_syntax::generated::nodes::AnyJsCallArgument"` but was unable to cast

npx @biomejs/biome lint . --apply does not crash, but appears to be running exceptionally low on this particular repository.

Expected result

Unsafe fixes to be applied.

Code of Conduct

• I agree to follow Biome's Code of Conduct

[wojtekmaj]

It might be related to #1144, but:

• Source location line is different (238 and not 230),
• I'm running the latest version od Biome, which is 1.6.4 at the time of writing.

[Sec-ant]

Hi, can you help us track down which file triggers this error and provide the code?

Also, which rules have you enabled in your configuration?

[wojtekmaj]

Sorry, I'm sort of a newbie in Biome, so that's all the info I got initially.

I tried to narrow down the issue and got a bit more info. Ended up with an example as simple as:

foo(<>{bar}</>);

Removal of any of the syntax included seems to make the issue go away. The following are NOT crashing:

(<>{bar}</>);

<>{bar}</>;

foo(<>{}</>);

foo(<></>);

Given that the only rule triggered with the above code is lint/complexity/noUselessFragments, that would be my suspect.

[Sec-ant]

@wojtekmaj This is very helpful, thank you for your time! I think this is an analyzer bug in the code action of noUselessFragments.