VS Code version

1.93.0

Extension version

2.3.0

Biome version

1.9.0

Operating system

• Windows
• macOS
• Linux

Description

When typing a comment line, if you input () within the comment, it unexpectedly moves to the end of the nearest non-empty line of code above it (please refer to the attached video).

This bug does not occur with regular end-of-line comments. It is consistently reproducible only with standalone comment lines (lines starting with // or /* */ comment blocks).

This issue arises when the Biome.js VS Code extension is enabled. To the best of my knowledge, the core @biomejs/biome package installed in node_modules is not related to this problem.
The bug occurs when the Biome.js VS Code extension is turned on and disappears when it's turned off.

Steps to reproduce

1. Open a JS/TS file in VS Code with the Biome.js extension enabled.
2. Start to input a comment line with // or /* */.
3. Type an opening parenthesis (. The editor will likely auto-insert the closing parenthesis ).
4. Manually type the closing parenthesis ).

The bug occurs at the moment you manually input the closing parenthesis, even if it was already auto-inserted by the editor.

Expected behavior

Nothing should happen.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

Logs

No response