.changeset/bright-tires-report.md (1)

9-14: Minor: Consider using js instead of ts for the code fence.

The example is valid JavaScript and doesn't require TypeScript-specific syntax, so marking it as js would be more precise. That said, ts is not incorrect since all valid JS is valid TS.

-```ts
+```js
 class classA {
 	C = C;
 }
 const C = 0;
-```
+```

crates/biome_js_analyze/src/lint/correctness/no_invalid_use_before_declaration.rs (2)

132-137: Factor out the repeated variable-scope ancestor lookup

The new declaration_scope / reference-scope comparison looks like the right mechanism to avoid cross‑scope false positives, and it should address the class value cases nicely. You are, however, repeating the same ancestors().skip(1).find(|a| AnyJsVariableScope::can_cast(a.kind())) pattern twice.

A small helper would tighten things up and make future tweaks to the scope definition less error‑prone, e.g.:

+fn variable_scope(node: &SyntaxNode) -> Option<SyntaxNode> {
+    node.ancestors().skip(1).find(|ancestor| AnyJsVariableScope::can_cast(ancestor.kind()))
+}
+
-            let declaration_scope = declaration
-                .syntax()
-                .ancestors()
-                .skip(1)
-                .find(|ancestor| AnyJsVariableScope::can_cast(ancestor.kind()));
+            let declaration_scope = variable_scope(declaration.syntax());
...
-                            declaration_scope == reference_syntax
-                                .ancestors()
-                                .skip(1)
-                                .find(|ancestor| AnyJsVariableScope::can_cast(ancestor.kind()))
+                            declaration_scope == variable_scope(reference_syntax)

Not a blocker, but it makes the intent a bit clearer for the next person reading the rule.

Also applies to: 160-165

---

301-318: Double‑check AnyJsVariableScope membership and consider a brief doc comment

The new AnyJsVariableScope union looks like a good capture of “roots that delay evaluation” (scripts/modules, functions, classes and TS modules/members), and it matches the cases exercised in valid.js.

Two small suggestions:

• Sanity‑check that this union covers all the places we want to treat as separate variable scopes for this rule (e.g. whatever node actually contains class field initialisers in your AST, if that is not always the class itself).
• Consider a short comment above the union explaining the intent (“Node kinds that define a separate value scope for noInvalidUseBeforeDeclaration”), so future rules do not accidentally misuse or extend it in the wrong direction.

Behaviour‑wise this looks sound; this is more about maintainability and future you not having to re‑reverse‑engineer the rationale.

crates/biome_js_analyze/tests/specs/correctness/noInvalidUseBeforeDeclaration/valid.js (1)

17-19: New valid cases nicely exercise the class value scenarios

These additions hit exactly the tricky spots: a class referencing itself in a static field, and a class field referencing a later class and const from the outer scope. That should keep the regression in #8148 firmly nailed down.

If you feel like being extra paranoid later, a variant using a static { ... } block would round out the coverage, but what you have here is already solid.

Also applies to: 21-26

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Learnt from: dyc3
Repo: biomejs/biome PR: 7081
File: packages/@biomejs/biome/configuration_schema.json:7765-7781
Timestamp: 2025-08-05T14:43:29.581Z
Learning: The file `packages/biomejs/biome/configuration_schema.json` is auto-generated and should not be manually edited or reviewed for schema issues; any changes should be made at the code generation source.

crates/biome_js_analyze/src/lint/correctness/no_invalid_use_before_declaration.rs (1)

132-137: Scope computation via AnyJsVariableScope fixes the class‑field false positive

Using AnyJsVariableScope::can_cast on both the declaration and reference ancestor chains cleanly separates references inside class bodies (or other scope roots) from top‑level declarations, so patterns like the new classA test no longer get reported. If you fancy a tiny tidy‑up, you could extract the repeated ancestors().skip(1).find(|ancestor| AnyJsVariableScope::can_cast(ancestor.kind())) into a helper, but it’s purely cosmetic.

Also applies to: 160-164

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Learnt from: dyc3
Repo: biomejs/biome PR: 7081
File: packages/@biomejs/biome/configuration_schema.json:7765-7781
Timestamp: 2025-08-05T14:43:29.581Z
Learning: The file `packages/biomejs/biome/configuration_schema.json` is auto-generated and should not be manually edited or reviewed for schema issues; any changes should be made at the code generation source.