crates/biome_js_analyze/src/lint/style/use_import_type.rs (2)

180-184: Bug: guard now disables the rule in far too many files.

is_none_or(|ext| ext != "cts") returns true for “no extension” and for any non-cts extension, so the rule bails out whenever import attributes are present in almost all cases. The intended behaviour (per prior discussion) is to bail only when the extension is explicitly present and not cts, leaving “no extension” paths unaffected.

Switch to is_some_and so “no extension” no longer short-circuits the rule.

Apply this diff:

-        if import_clause.attribute().is_some()
-            && ctx.file_path().extension().is_none_or(|extension| extension != "cts")
-            && !matches!(ctx.root(), AnyJsRoot::JsScript(_))
-        {
+        if import_clause.attribute().is_some()
+            && ctx.file_path()
+                .extension()
+                .is_some_and(|extension| extension != "cts")
+            && !matches!(ctx.root(), AnyJsRoot::JsScript(_))
+        {
             return None;
         }

---

756-771: Fixer can silently no-op when a specifier has no leading trivia.

specifier.syntax().first_leading_trivia()? may be None (e.g. import type {A} from "mod";). The ? then aborts the whole action, so no fix is produced. Also, moving the specifier’s leading trivia onto the newly inserted type token risks mangling comments.

Prefer a simpler, safer insertion that doesn’t depend on existing trivia.

Apply this diff:

-                for specifier in specifiers {
-                    let new_specifier = specifier
-                        .clone()
-                        .with_leading_trivia_pieces([])?
-                        .with_type_token(Some(
-                            make::token(T![type])
-                                .with_leading_trivia_pieces(
-                                    specifier.syntax().first_leading_trivia()?.pieces(),
-                                )
-                                .with_trailing_trivia([(TriviaPieceKind::Whitespace, " ")]),
-                        ));
-                    mutation.replace_node(specifier.clone(), new_specifier);
-                }
+                for specifier in specifiers {
+                    let new_specifier = specifier.clone().with_type_token(Some(
+                        make::token(T![type])
+                            .with_trailing_trivia([(TriviaPieceKind::Whitespace, " ")]),
+                    ));
+                    mutation.replace_node(specifier.clone(), new_specifier);
+                }

If you want to preserve comments strictly before the identifier (e.g. /* id */ A), keep them attached to the specifier (not the type token). The formatter will normalise spacing between type and the identifier.

crates/biome_js_analyze/src/lint/style/use_import_type.rs (1)

764-775: Handle specifiers without leading trivia; current code can noop the fix.

specifier.syntax().first_leading_trivia()? can be absent (e.g. import type {A} without spaces). The ? will abort the whole action, so no fix is applied. Use a best-effort approach: steal trivia when present; otherwise, just insert type with no extra leading trivia.

Suggested change:

-                    let new_specifier = specifier
-                        .clone()
-                        .with_leading_trivia_pieces([])?
-                        .with_type_token(Some(
-                            make::token(T![type])
-                                .with_leading_trivia_pieces(
-                                    specifier.syntax().first_leading_trivia()?.pieces(),
-                                )
-                                .with_trailing_trivia([(TriviaPieceKind::Whitespace, " ")]),
-                        ));
+                    let mut type_tok = make::token(T![type])
+                        .with_trailing_trivia([(TriviaPieceKind::Whitespace, " ")]);
+                    if let Some(trivia) = specifier.syntax().first_leading_trivia() {
+                        type_tok = type_tok.with_leading_trivia_pieces(trivia.pieces());
+                    }
+                    let new_specifier = specifier
+                        .clone()
+                        // Drop the specifier's original leading trivia so it becomes owned by `type`
+                        .with_leading_trivia_pieces([])?
+                        .with_type_token(Some(type_tok));

Would you like me to add a test case for import type {A} (no spaces) to ensure this path is covered?