.changeset/tame-dolls-serve.md (1)

5-5: Spell out patterns and runes for clarity (tiny polish).

Listing the exact patterns and Svelte 5 runes makes the note clearer and more searchable. Also adds a present‑tense sentence to describe current behaviour.

Apply this diff:

-Added support for automatically recognizing Svelte globals ($state and so on) inside `.svelte.test.ts/js` `.svelte.spec.ts/js` files.
+Added support for automatically recognizing Svelte 5 globals ($bindable, $derived, $effect, $host, $inspect, $props, $state) in files with the following patterns: `.svelte.test.ts`, `.svelte.test.js`, `.svelte.spec.ts`, `.svelte.spec.js`.
+These globals are now available in those test files as well.

(Optional) You could add a tiny example after the sentence:

```svelte
<!-- Button.svelte.test.ts -->
<script lang="ts">
  let count = $state(0);
  $effect(() => console.log(count));
</script>

</blockquote></details>
<details>
<summary>crates/biome_service/src/file_handlers/javascript.rs (2)</summary><blockquote>

`325-333`: **Consolidate suffix checks to reduce repetition.**

A single any() over a small slice improves readability and makes future additions simpler.



Apply this diff:

```diff
-            } else if filename.ends_with(".svelte")
-                || filename.ends_with(".svelte.js")
-                || filename.ends_with(".svelte.ts")
-                || filename.ends_with(".svelte.test.ts")
-                || filename.ends_with(".svelte.test.js")
-                || filename.ends_with(".svelte.spec.ts")
-                || filename.ends_with(".svelte.spec.js")
-            {
+            } else if [
+                ".svelte",
+                ".svelte.js",
+                ".svelte.ts",
+                ".svelte.test.ts",
+                ".svelte.test.js",
+                ".svelte.spec.ts",
+                ".svelte.spec.js",
+            ]
+            .iter()
+            .any(|s| filename.ends_with(s))
+            {

---

325-346: Consider adding tests for these new patterns.

A couple of assertions in javascript.tests.rs that AnalyzerOptions.globals includes the Svelte runes for .svelte.test.ts/.js and .svelte.spec.ts/.js would lock this in and prevent regressions.

If you’d like, I can sketch the test cases asserting the presence of $state (and friends) for those filenames.

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-08-11T11:43:46.619Z
Learning: Applies to crates/biome_analyze/**/src/lint/nursery/**/*.rs : Set the language field in declare_lint_rule! to the primary language/dialect (js, jsx, ts, tsx)

.changeset/tame-dolls-serve.md (1)

5-6: Tighten wording, expand patterns explicitly, and list the globals.

Avoid “and so on”, state the current behaviour in present tense, and spell out the four patterns to remove ambiguity. Adding a tiny representative example also aligns with the changeset guidelines.

Apply this diff:

-Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside `.svelte.test.ts/js` and `.svelte.spec.ts/js` files.
+Fixed Svelte globals detection in test and spec files.
+
+Svelte globals ($bindable, $derived, $effect, $host, $inspect, $props, $state) are now recognised in `.svelte.test.ts`, `.svelte.test.js`, `.svelte.spec.ts`, and `.svelte.spec.js` files. This matches the behaviour for regular `.svelte`, `.svelte.ts`, and `.svelte.js` files.
+
+Example.
+
+```svelte
+<!-- Example: Counter.svelte.test.ts -->
+<script lang="ts">
+  const count = $state(0);
+  $effect(() => console.log(count));
+</script>
+```

Optional: consider linking to the official Svelte runes documentation and/or the tracking issue for this fix.

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.