`biome check --write --unsafe` hangs indefinitely with `noCommentText` fix

[Bug-Finderr]

Environment

• Biome version: 2.4.4
• OS: macOS (Darwin 25.3.0)

Description

biome check --write --unsafe hangs indefinitely when a TSX file has a noCommentText violation. The unsafe fix (// comment → {/* comment */}) creates an infinite fix cycle.

• biome check → reports error, exits normally
• biome check --write → skips unsafe fix, exits normally
• biome check --write --unsafe → hangs forever

Reproduction

Playground link

mkdir /tmp/biome-repro && cd /tmp/biome-repro

cat > biome.json << 'EOF'
{
  "formatter": { "enabled": true, "indentStyle": "space", "indentWidth": 2 },
  "linter": { "enabled": true, "rules": { "recommended": true } }
}
EOF

cat > test.tsx << 'EOF'
export default function Foo() {
  return (
    <div>
      <p>// comment</p>
    </div>
  );
}
EOF

biome check --write --unsafe test.tsx
# Hangs — kill with Ctrl+C

[github-actions]

Hello @Bug-Finderr, 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]

Please share with us a minimal reproduction. Follow the bot instructions to create one

[Because789]

I have a project with a lot of nursery/useSortedClasses and some other violations. In my case biome check --write --unsafe doesn't "hang", but it simply refuses to apply any fix at all. I wonder if that is connected to your issue. I will try to get to a minimal reproduction when I have time....

[Bug-Finderr]

@ematipico I've updated the issue; my initial analysis was completely wrong. The root cause is noCommentText, not useSortedClasses. Minimal repro is just a bare // comment inside JSX children with --write --unsafe.

Playground link

@Because789 Sorry for the misleading report; your issue with useSortedClasses fixes not applying might be a separate bug. Apologies for the confusion.

[Bug-Finderr]

The unsafe fix converts // text to {/* text */}, which turns visible rendered text into an invisible JSX comment. If I intentionally wanted to display "// text", the fix silently removes it.
Maybe the fix should produce {'// text'} instead? The original ESLint rule doesn't auto-fix at all; it only reports.