crates/biome_js_analyze/src/lint/nursery/no_unsafe_assignment.rs (1)

105-122: Consider narrowing the diagnostic range to just the expression.

Currently initializer.range() covers = getPayload() including the = token. Using expression.range() instead would point directly at the any-typed value. This is a minor UX polish — entirely optional.

Proposed diff

     fn diagnostic(ctx: &RuleContext<Self>, _state: &Self::State) -> Option<RuleDiagnostic> {
         let declarator = ctx.query();
         let initializer = declarator.initializer()?;
+        let expression = initializer.expression().ok()?;
         Some(
             RuleDiagnostic::new(
                 rule_category!(),
-                initializer.range(),
+                expression.range(),
                 markup! {
                     "The assigned expression has the type "<Emphasis>"any"</Emphasis>", which undermines type safety."
                 },

crates/biome_js_analyze/tests/specs/nursery/noUnsafeAssignment/valid.ts (1)

23-24: Nitpick: readFileSync doesn't exist on node:fs/promises.

The test still works (the type is unresolved either way), but using fs.readFile(...) or importing from "node:fs" would be more accurate for anyone reading this as an example.