Merge pull request #7708 from biomejs/next

Author: ematipico

.changeset/based-bears-brawl.md

@@ -0,0 +1,28 @@
+---
+"@biomejs/biome": minor
+---
+
+Biome's resolver now supports `baseUrl` if specified in `tsconfig.json`.
+
+#### Example
+
+Given the following file structure:
+
+**`tsconfig.json`**
+```json
+{
+    "compilerOptions": {
+        "baseUrl": "./src",
+    }
+}
+```
+
+**`src/foo.ts`**
+```ts
+export function foo() {}
+```
+
+In this scenario, `import { foo } from "foo";` should work regardless of the
+location of the file containing the `import` statement.
+
+Fixes [#6432](https://github.com/biomejs/biome/issues/6432).

.changeset/breezy-suns-leave.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+Added `ignore` option to `noUnknownAtRules`. If an unknown at-rule matches any of the items provided in `ignore`, a diagnostic won't be emitted.

.changeset/busy-pens-send.md

@@ -0,0 +1,26 @@
+---
+"@biomejs/biome": minor
+---
+
+Enhanced the `init` command. The `init` command now checks if the existing project contains known ignore files and known generated folders.
+
+If Biome finds `.gitignore` or `.ignore` files, it will add the following configuration to `biome.json`:
+```diff
+{
++  "vcs": {
++    "enabled": true,
++    "clientKind": "git",
++    "useIgnoreFile": true
++  }
+}
+```
+
+If Biome finds a `dist/` folder, it will exclude it automatically using the double-exclude syntax:
+
+```diff
+{
++  "files": {
++    "includes": ["**", "!!**/dist"]
++  }
+}
+```

.changeset/crazy-steaks-mix.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

.changeset/css-parse-modules-flag.md

@@ -0,0 +1,14 @@
+---
+"@biomejs/biome": minor
+---
+
+Added `--css-parse-css-modules` CLI flag to control whether CSS Modules syntax is enabled.
+
+You can now enable or disable CSS Modules parsing directly from the command line:
+
+```shell
+biome check --css-parse-css-modules=true file.module.css
+biome format --css-parse-css-modules=true file.module.css
+biome lint --css-parse-css-modules=true file.module.css
+biome ci --css-parse-css-modules=true file.module.css
+```

.changeset/css-parse-tailwind-flag.md

@@ -0,0 +1,14 @@
+---
+"@biomejs/biome": minor
+---
+
+Added `--css-parse-tailwind-directives` CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.
+
+You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:
+
+```shell
+biome check --css-parse-tailwind-directives=true file.css
+biome format --css-parse-tailwind-directives=true file.css
+biome lint --css-parse-tailwind-directives=true file.css
+biome ci --css-parse-tailwind-directives=true file.css
+```

.changeset/dull-drinks-switch.md

@@ -0,0 +1,12 @@
+---
+"@biomejs/biome": minor
+---
+
+Updated the formatting of `.svelte` and `.vue` files. Now the indentation of the JavaScript blocks matches Prettier's:
+
+```diff
+<script>
+- import Component from "./Component"
++   import Component from "./Component"
+</script>
+```

.changeset/eager-suns-smoke.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.

.changeset/few-bees-reply.md

@@ -0,0 +1,24 @@
+---
+"@biomejs/biome": minor
+---
+
+Implemented the `indentScriptAndStyle` option for vue and svelte files, with the default set to `false` to match [Prettier's `vueIndentScriptAndStyle` option](https://prettier.io/docs/options#vue-files-script-and-style-tags-indentation). When enabled, this option indents the content within `<script>` and `<style>` tags to align with the surrounding HTML structure.
+
+It can be enabled with this configuration:
+
+```json
+{
+  "html": {
+    "formatter": {
+      "indentScriptAndStyle": true
+    }
+  }
+}
+```
+
+Which will format this code to:
+```vue
+<script>
+  import Component from "./Component.vue";
+</script>
+```

.changeset/forced-files-forget.md

@@ -0,0 +1,44 @@
+---
+"@biomejs/biome": minor
+---
+
+Deprecated the option `files.experimentalScannerIgnores` in favour of **force-ignore** syntax in `files.includes`.
+
+`files.includes` supports ignoring files by prefixing globs with an exclamation mark (`!`). With this change, it also supports _force_-ignoring globs by prefixing them with a double exclamation mark (`!!`).
+
+The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested `biome.json` files.
+
+#### Example
+
+Let's take the following configuration:
+
+```json
+{
+    "files": {
+        "includes": [
+            "**",
+            "!**/generated",
+            "!!**/dist",
+            "fixtures/example/dist/*.js"
+        ]
+    },
+    "linter": {
+        "domains": {
+            "project": "all"
+        }
+    }
+}
+```
+
+This configuration achieves the following:
+
+- Because the [project domain](https://biomejs.dev/linter/domains/#project) is enabled, all supported files in the project are indexed _and_ processed by the linter, _except_:
+- Files inside a `generated` folder are not processed by the linter, but they will get indexed _if_ a file outside a `generated` folder imports them.
+- Files inside a `dist` folder are never indexed nor processed, not even if they are imported for any purpose, _except_:
+- When the `dist` folder is inside `fixtures/example/`, its `.js` files _do_ get both indexed and processed.
+
+In general, we now recommend using the force-ignore syntax for any folders that contain _output_ files, such as `build/` and `dist/`. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.
+
+`experimentalScannerIgnores` will continue to work for now, but you'll see a deprecation warning if you still use it.
+
+Run the `biome migrate --write` command to automatically update the configuration file.