release: 1.6.0

.github/ISSUE_TEMPLATE/01_formatter_bug.yml

@@ -15,7 +15,7 @@ body:
     id: environment
     attributes:
       label: Environment information
-      description: Run the command `biome rage` and paste its output here. Please review it, in case there are sensitive information you don't want to share.
+      description: Run the command `biome rage --formatter` and paste its output here. Please review it, in case there are sensitive information you don't want to share.
       render: bash
     validations:
       required: true

.github/ISSUE_TEMPLATE/02_lint_bug.yml

@@ -15,7 +15,7 @@ body:
     id: environment
     attributes:
       label: Environment information
-      description: Run the command `biome rage` and paste its output here. Please review it, in case there are sensitive information you don't want to share.
+      description: Run the command `biome rage --linter` and paste its output here. Please review it, in case there are sensitive information you don't want to share.
       render: bash
     validations:
       required: true

CHANGELOG.md

@@ -9,7 +9,7 @@ New entries must be placed in a section entitled `Unreleased`.
 Read
 our [guidelines for writing a good changelog entry](https://github.com/biomejs/biome/blob/main/CONTRIBUTING.md#changelog).
 
-## Unreleased
+## 1.6.0 (TBD)
 
 ### Analyzer
 

crates/biome_service/src/file_handlers/vue.rs

@@ -63,7 +63,7 @@ impl VueFileHandler {
 
     /// Returns the start byte offset of the Vue `<script>` tag
     pub fn start(input: &str) -> Option<u32> {
-        Self::matches_script(input).map(|m| m.start() as u32 - 1)
+        Self::matches_script(input).map(|m| m.start() as u32)
     }
 
     fn matches_script(input: &str) -> Option<Match> {

package.json

@@ -3,9 +3,9 @@
 	"private": true,
 	"version": "0.0.0",
 	"scripts": {
-		"check:apply": "cargo biome-cli-dev check --apply-unsafe editors website packages/@biomejs/js-api packages/tailwindcss-config-analyzer",
-		"check": "cargo biome-cli-dev check editors website packages/@biomejs/js-api packages/tailwindcss-config-analyzer",
-		"ci": "cargo biome-cli-dev ci editors website packages/@biomejs/js-api packages/tailwindcss-config-analyzer"
+		"check:apply": "cargo biome-cli-dev check --apply-unsafe website packages/@biomejs/js-api packages/tailwindcss-config-analyzer",
+		"check": "cargo biome-cli-dev check website packages/@biomejs/js-api packages/tailwindcss-config-analyzer",
+		"ci": "cargo biome-cli-dev ci website packages/@biomejs/js-api packages/tailwindcss-config-analyzer"
 	},
 	"keywords": [],
 	"author": "",

packages/@biomejs/biome/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@biomejs/biome",
-    "version": "1.5.3",
+    "version": "1.6.0",
     "bin": "bin/biome",
     "scripts": {
         "postinstall": "node scripts/postinstall.js"

website/astro.config.ts

@@ -240,7 +240,6 @@ export default defineConfig({
 						{
 							label: "Git Hooks",
 							link: "/recipes/git-hooks",
-							badge: "New",
 						},
 					],
 				},

website/src/components/BlogPostInfo.astro

@@ -27,7 +27,7 @@ const authors = await getAuthorsData(
     {
       authors.map(({ data: author }) => (
         <span class="avatar">
-          <Image src={author.avatar} alt="" height="36" width="36" />
+          <Image src={author.avatar} alt="" height="36" width="36" loading="eager" />
         </span>
       ))
     }

website/src/content/blog/biome-v1-5.md

@@ -12,7 +12,7 @@ pubDate: 2024-01-08
 coverImage:
   lightSrc: "@/assets/blog/roadmap-2024/banner-light.png"
   darkSrc: "@/assets/blog/roadmap-2024/banner-dark.png"
-  alt: The Prettier challenge banner, with the Biome logo over it
+  alt: The brand of the project. It says "Biome, toolchain of the web"
 socialImage: "@/assets/social-logo.png"
 ---
 

website/src/content/blog/biome-v1-6.mdx

@@ -0,0 +1,228 @@
+---
+title: Biome v1.6
+description: Partial support for Astro, Svelte and Vue, extend configuration from dependencies, formatter goodies.
+summary: |
+  Partial support for Astro, Svelte and Vue files, both CLI and LSP.
+  Now, the `extends` field is able to pick configuration files that are exported as a dependency, very useful in monorepo and big projects.
+  The formatter has new options.
+authors:
+  - ema
+  - team
+pubDate: 2024-03-08
+coverImage:
+  lightSrc: "@/assets/blog/roadmap-2024/banner-light.png"
+  darkSrc: "@/assets/blog/roadmap-2024/banner-dark.png"
+  alt: The brand of the project. It says "Biome, toolchain of the web"
+socialImage: "@/assets/social-logo.png"
+---
+
+import { Tabs, TabItem } from '@astrojs/starlight/components';
+import { Image } from "astro:assets";
+import astroLint from "../../assets/blog/biome-v1-6/astro-linter.png"
+import vueLint from "../../assets/blog/biome-v1-6/vue-linter.png"
+import svelteLint from "../../assets/blog/biome-v1-6/svelte-linter.png"
+
+Update Biome using the following commands:
+
+```shell
+npm install --save-dev --save-exact @biomejs/biome@latest
+npx @biomejs/biome migrate
+```
+
+## Partial support for Astro, Svelte and Vue files
+
+In this release, we're happy to provide partial support for Astor, Svelte and Vue files. What does **partial** support mean?
+
+While the team is working on a [unified data structure](https://github.com/biomejs/biome/discussions/1726) for HTML-ish languages, we discovered that we could provide Biome functionalities to those files with just few changes, albeit some expectations.
+
+This means that Biome is able to analyse the JavaScript/TypeScript portion of said files, and all features are available: formatting, linting and import sorting! Here's an example that you should expect in terms of developer experience:
+
+<Tabs>
+    <TabItem label="Astro" icon="astro">
+        <div align="center">
+            <Image src={astroLint} alt="Screenshot of Biome linting in action for an Astro file in VSCode" width="500"  />
+        </div>
+    </TabItem>
+    <TabItem label="Vue" icon="seti:vue">
+        <div align="center">
+            <Image src={vueLint} alt="Screenshot of Biome linting in action for an Vue file in VSCode" width="500"  />
+        </div>
+    </TabItem>
+    <TabItem label="Svelte" icon="seti:svelte">
+        <div align="center">
+            <Image src={svelteLint} alt="Screenshot of Biome  linting in action for an Svelte file in VSCode" width="500"  />
+        </div>
+    </TabItem>
+</Tabs>
+
+Make sure to read the [documentation about expectations and limitations](/internals/language-support#html-super-languages-support).
+
+## Configuration, lighter and more powerful
+
+### Support for `biome.jsonc`
+
+Biome now accepts the file `biome.jsonc` as configuration! Now, you can insert all the comments you want in a configuration.
+
+### `extends` resolves dependencies
+
+From this version, Biome can the `extends` property can *resolve* other configuration files that are installed and exported as a dependency.
+
+There are few important steps in order to make the configuration discoverable. The file must be exported from a `"module"` package, and the file should be exported in your `package.json` like this:
+
+```json name="shared-configs/package.json"
+{
+  "name": "@shared-configs",
+  "type": "module",
+  "exports": {
+    "./biome": "./biome.json"
+  }
+}
+```
+
+This set up allows to expose a specifier `@shared-configs/biome`, which you use inside your `biome.json` file.
+
+```json name="project/biome.json"
+{
+  "extends": ["@shared-configs/biome"]
+}
+```
+
+The resolution of the dependencies is powered by the library [`oxc-resolver`](https://github.com/oxc-project/oxc-resolver), one of the many libraries provided by the [OXC project](https://oxc-project.github.io/). It's battle-tested and spec compliant!
+
+:::note
+You can also export `biome.jsonc` files!
+
+```json name="shared-configs/package.json" ins="./biome.jsonc"
+{
+  "name": "@shared-configs",
+  "type": "module",
+  "exports": {
+    "./biome": "./biome.jsonc"
+  }
+}
+```
+:::
+
+### Reduced memory footprint
+
+We **reduced** the size our configuration **by a factor of 6.5**! This change might not have massive effects on the speed of the program, but it greatly reduced the memory used when running the CLI or the LSP.
+
+## New formatting options
+
+Other than fixes, the formatter provides two new options that should improve the compatibility with Prettier parity
+
+### Option `attributePosition`
+
+The contributor [@octoshikari](https://github.com/octoshikari) implemented this new feature by themselves! Huge thank you for helping the Biome project.
+
+When `formatter.attributePosition` has the value `multiline`, all attributes of HTML-ish languages (JSX/TSX as for time of writing) will be collapsed on multiple lines regardless of their numbers:
+
+
+<div class="card">
+    <div class="card-column">
+        <h4>With variant `auto` (default)</h4>
+        The attributes are automatically formatted, and they will collapse in multiple lines only when they hit certain criteria.
+
+        ```jsx title="file.jsx"
+        <Button as="link" style="primary" href="https://example.com">
+            Hit me
+        </Button>
+        ```
+    </div>
+    <div class="card-column">
+        <h4>With variant `multiline`</h4>
+        The attributes are always formatted on multiple lines, regardless.
+
+        ```jsx title="file.jsx"
+        <Button
+            as="link"
+            style="primary"
+            href="https://example.com"
+        >
+            Hit me
+        </Button>
+        ```
+    </div>
+</div>
+
+
+### Option `json.formatter.trailingComma`
+
+Previously, Biome parser introduced an option that would allow to parse JSON and JSONC files that contained a trailing comma. This was required to ease the friction caused by other tools that
+tolerate trailing commas by default (e.g. VSCode, Prettier, etc.).
+
+Although, our formatter wasn't as tolerant. With the option `json.formatter.trailingComma`, you can apply the same rules that `js.formatter.trailingComma` applies.
+
+<div class="card">
+    <div class="card-column">
+        <h4>With variant `none` (default)</h4>
+        The formatter removes the trailing comma upon formatting.
+
+        ```json title="file.json" ins="\"ipsum_last\""
+        {
+            "lorem": "ipsum",
+            "lorem": "ipsum",
+            "lorem": "ipsum",
+            "lorem": "ipsum_last"
+        }
+        ```
+    </div>
+    <div class="card-column">
+        <h4>With variant `all`</h4>
+        The formatter adds the trailing comma upon formatting.
+
+        ```json title="file.json" ins="\"ipsum_last\","
+        {
+            "lorem": "ipsum",
+            "lorem": "ipsum",
+            "lorem": "ipsum",
+            "lorem": "ipsum_last",
+        }
+        ```
+    </div>
+</div>
+
+## Easier migration from Prettier
+
+This release introduces a new command called `biome migrate prettier`. This command will read your Prettier `.prettierrc`/`prettier.json` and `.prettierignore`, and attempt to port its options and globs in Biome.
+
+Given a `prettier.json` file, Biome will **modify** the existing configuration file to match Prettier's options:
+
+```json title="prettier.json"
+{ "useTabs": false, "semi": true, "singleQuote": true }
+```
+
+```json title="biome.json"
+{
+  "formatter": {
+    "enabled": true,
+    "formatWithErrors": false,
+    "indentStyle": "space",
+    "indentWidth": 2,
+    "lineEnding": "lf",
+    "lineWidth": 80,
+    "attributePosition": "auto"
+  },
+  "linter": { "enabled": true },
+  "javascript": {
+    "formatter": {
+      "jsxQuoteStyle": "double",
+      "quoteProperties": "asNeeded",
+      "trailingComma": "all",
+      "semicolons": "always",
+      "arrowParentheses": "always",
+      "bracketSpacing": true,
+      "bracketSameLine": false,
+      "quoteStyle": "single",
+      "attributePosition": "auto"
+    }
+  }
+}
+```
+
+:::caution
+Due to the different nature of `.prettierignore` globs and Biome’s globs, it’s **highly advised** to make sure that those globs still work under Biome.
+Prettier's globs are **git globs**, while Biome's globs are **unix-style** globs.
+:::
+
+###

website/src/content/docs/guides/getting-started.mdx

@@ -59,9 +59,28 @@ After running the `init` command, you'll now have a new `biome.json` file in you
 }
 ```
 
+Alternatively, you can run `biome init --jsonc` , and emit a `biome.jsonc` file:
+
+<PackageManagerBiomeCommand command="init --jsonc" />
+
+```json title="biome.jsonc"
+{
+  "$schema": "https://biomejs.dev/schemas/1.5.3/schema.json",
+  "organizeImports": {
+    "enabled": false
+  },
+  "linter": {
+    "enabled": true,
+    "rules": {
+      "recommended": true
+    }
+  }
+}
+```
+
 The `linter.enabled: true` enables the linter and `rules.recommended: true` enables the [recommended rules](/linter/rules/).
 
-Formatting is enabled because the configuration doesn't explicitly [disable](/reference/configuration/#formatterenabled) formatting with `formatter.enabled: false`.
+Formatting is enabled **by default**, because the configuration doesn't explicitly [disable](/reference/configuration/#formatterenabled) formatting with `formatter.enabled: false`.
 
 ## Usage
 

website/src/content/docs/guides/how-biome-works.mdx

@@ -125,9 +125,10 @@ From version `v1.6.0`, Biome is able to resolve configuration files from `node_m
 
 In order to do so, the first thing to do is to set up your "shared" Biome configuration in a certain way. Let's suppose that your library is called `@org/shared-configs`, and you want to import the Biome configuration using the specifier `@org/shared-configs/biome`. You have to set up the `package.json` is a specific way:
 
-```json title="package.json" ins={4}
+```json title="package.json" ins={5,3}
 {
   "name": "@org/shared-configs",
+  "type": "module",
   "exports": {
     "./biome": "./biome.json"
   }

website/src/content/docs/internals/changelog.md

@@ -15,7 +15,7 @@ New entries must be placed in a section entitled `Unreleased`.
 Read
 our [guidelines for writing a good changelog entry](https://github.com/biomejs/biome/blob/main/CONTRIBUTING.md#changelog).
 
-## Unreleased
+## 1.6.0 (TBD)
 
 ### Analyzer