chore: next

.changeset/add_new_option_javascriptjsxeverywhere.md

@@ -0,0 +1,9 @@
+---
+"@biomejs/biome": minor
+---
+
+Add new option `javascript.parser.jsxEverywhere`. This new option allows to control whether Biome should expect JSX syntax in `.js`/`.ts` files.
+
+When `jsxEverywhere` is set to `false`, having JSX syntax like `<div></div>` inside `.js`/`.ts` files will result in a **parsing error**.
+
+This option defaults to `true`.

.changeset/add_the_new_rule_nofloatingpromises.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+Add the new rule [`noFloatingPromises`](https://biomejs.dev/linter/rules/no-floating-promises).

.changeset/add_the_new_rule_noimportcycles.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+Add the new rule [`noImportCycles`](https://biomejs.dev/linter/rules/no-import-cycles).

.changeset/add_the_new_rule_notsignorehttps.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+Add the new rule [`noTsIgnore`](https://biomejs.dev/linter/rules/no-ts-ignore).

.changeset/add_the_new_rule_nounwantedpolyfillio.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+Add the new rule [`noUnwantedPolyfillio`](https://biomejs.dev/linter/rules/no-unwanted-polyfillio).

.changeset/add_whitespace_after_css_selecters_preceded_by_comment.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+Fix [#5001](https://github.com/biomejs/biome/issues/5001), where the CSS formatter removes whitespace from selector preceded by a comment

.changeset/added_a_json_format_option_expandslists.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": minor
+---
+
+Added a JSON format option `expand`. The option `json.formatter.expand` allows to enforce the formatting of arrays and objects on multiple lines, regardless of their length.

.changeset/better_control_over_linter_groups.md

@@ -0,0 +1,30 @@
+---
+"@biomejs/biome": minor
+---
+
+Linter groups now accept new options to enable/disable all rules that belong to a group, and control the severity
+of the rules that belong to those groups.
+
+For example, you can downgrade the severity of rules that belong to `"style"` to emit `"info"` diagnostics:
+
+```json
+{
+  "linter": {
+    "rules": {
+      "style": "info"
+    }
+  }
+}
+```
+
+You can also enable all rules that belong to a group using the default severity of the rule using the `"on"` option:
+
+```json
+{
+  "linter": {
+    "rules": {
+      "complexity": "on"
+    }
+  }
+}
+```

.changeset/biome_assist.md

@@ -0,0 +1,53 @@
+---
+"@biomejs/biome": minor
+---
+
+Biome assist is a new feature of the Biome analyzer. The assist is meant to provide **actions**. Actions differ from linter rules in that they aren't meant to signal errors.
+
+The assist will provide code actions that users can opt into via configuration or via IDEs/editors, using the Language Server Protocol.
+
+The assist **is enabled by default**.  However, you can turn if off via configuration:
+
+```json
+{
+  "assist": {
+    "enabled": false
+  }
+}
+```
+
+You can turn on the actions that you want to use in your configuration. For example, you can enable the `useSortedKeys` action like this:
+
+```json
+{
+  "assist": {
+    "actions": {
+      "source": {
+        "useSortedKeys": "on"
+      }
+    }
+  }
+}
+```
+
+Alternatively, IDE/editor users can decide which action to apply on save *directly from the editor settings*, as long as the assist is enabled.
+
+For example, in VS Code you can apply the `useSortedKeys` action when saving a file by adding the following snippet in `settings.json`:
+
+```json
+{
+  "editor.codeActionsOnSave": {
+    "source.biome.useSortedKeys": "explicit"
+  }
+}
+```
+
+In Zed, you can achieve the same by adding the following snippet in `~/.config/zed/settings.json`:
+
+```json
+{
+  "code_actions_on_format": {
+    "source.biome.useSortedKeys": true
+  }
+}
+```

.changeset/biome_logs_a_warning_in_case_a_folder_contains_biomejson_and_biomejsonc_and_it_will_use_biomejson_by_default.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+Biome logs a warning in case a folder contains `biome.json` and `biome.jsonc`, and it will use `biome.json` by default.

.changeset/biome_migrate_eslint_rule_overriding.md

@@ -0,0 +1,38 @@
+---
+"@biomejs/biome": minor
+---
+
+Biome migrate eslint outputs a better overriding behavior.
+
+A Biome rule can have multiple ESLint equivalent rules.
+For example, [useLiteralKeys](https://biomejs.dev/linter/rules/use-literal-keys/) has two ESLint equivalent rules: [dot-notation](https://eslint.org/docs/latest/rules/dot-notation) and [@typescript-eslint/dot-notation](https://typescript-eslint.io/rules/dot-notation/).
+
+Previously, Biome wouldn't always enable a Biome rule even if one of its equivalent rules was enabled.
+Now Biome uses the higher severity level of all the equivalent ESLint rules to set the severity level of the Biome rule.
+
+The following ESLint configuration...
+
+```json
+{
+  "rules": {
+    "@typescript-eslint/dot-notation": "error",
+    "dot-notation": "off"
+  }
+}
+```
+
+...is now migrated to...
+
+```json
+{
+  "linter": {
+    "rules": {
+      "complexity": {
+        "useLiteralKeys": "error"
+      }
+    }
+  }
+}
+```
+
+...because `error` is higher than `off`.

.changeset/biome_now_resolves_globs_and_paths_from_the_configuration_before_paths_and_globs_were_resolved_from_the_working_directory.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": major
+---
+
+Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

.changeset/code_actions_via_ideeditor.md

@@ -0,0 +1,35 @@
+---
+"@biomejs/biome": minor
+---
+
+Biome users can now configure code actions from linter rules as well as assist actions directly in the settings of their IDE/editor.
+
+For example, let's consider the lint rule [`noSwitchDeclarations`](https://biomejs.dev/linter/rules/no-switch-declarations/), which has an unsafe fix.
+Previously, if you wanted to use this rule, you were "forced" to enable it via configuration, and if you wanted to apply its fix when you saved a file, you were forced to mark the fix as safe:
+
+```json
+{
+  "linter": {
+    "rules": {
+      "correctness": {
+        "noSwitchDeclarations": {
+          "level": "error",
+          "fix": "safe"
+        }
+      }
+    }
+  }
+}
+```
+
+Now, you can benefit from the code action without making the fix safe for the entire project. IDEs and editors that are LSP compatible allow to list a series of "filters" or code actions that can be applied on save. In the case of VS Code, you will need to add the following snippet in the `settings.json`:
+
+```json
+{
+  "editor.codeActionsOnSave": {
+    "quickfix.biome.correctness.noSwitchDeclarations": "explicit"
+  }
+}
+```
+
+Upon save, Biome will inform the editor the apply the code action of the rule `noSwitchDeclarations`.

.changeset/config.json

@@ -0,0 +1,21 @@
+{
+  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+  "changelog": ["@changesets/changelog-github", { "repo": "withastro/astro" }],
+  "commit": false,
+  "fixed": [
+    [
+      "@biomejs/biome",
+      "@biomejs/cli-*",
+      "@biomejs/wasm-*"
+    ]
+  ],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": [
+    "@biomejs/benchmark",
+    "@biomejs/aria-data",
+    "tailwindcss-config-analyzer"
+  ]
+}

.changeset/enable_rule_with_default_severity.md

@@ -0,0 +1,33 @@
+---
+"@biomejs/biome": minor
+---
+
+You can now enable lint rules using the default severity suggested by Biome using the new variant `"on"`, when enabling a rule.
+
+For example, the default severity of the rule `style.noVar` is `error`, so you would use `"on"`, and  then linting a code that uses `var`, will result in an error:
+
+```json
+{
+  "linter": {
+    "recommended": false,
+    "rules": {
+      "style": {
+        "noVar": "on"
+      }
+    }
+  }
+}
+```
+
+```js
+// main.js
+var name = "tobias"
+```
+
+The command `biome lint main.js` will result in an error due to the default severity assigned to `noVar`.
+
+Refer to the documentation page of each rule to know their suggested diagnostic severity, or use the command `biome explain <RULE_NAME>`:
+
+```shell
+biome explain noVar
+```

.changeset/export_named_type_parser.md

@@ -0,0 +1,11 @@
+---
+"@biomejs/biome": patch
+---
+
+Export Named Type support `default` parser.
+
+The following code is now parsed successfully:
+
+```ts
+export { type A as default } from './b.ts';
+```

.changeset/fix_1597_useexhaustivedependencies_now_consider_react_hooks_stable_within_parentheses_or_type_assertions.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+Fix #1597, useExhaustiveDependencies now consider React hooks stable within parentheses or type assertions.

.changeset/fix_a_bug_where_config_path_accepted_configuration_files_with_unsupported_extensions.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+Fix a bug where `--config-path` accepted configuration files with unsupported extensions. Now only `.json` and `.jsonc` are accepted, and an error is raised otherwise.

.changeset/fix_fragament_4751.md

@@ -0,0 +1,24 @@
+---
+"@biomejs/biome": patch
+---
+
+Fix [#4751](https://github.com/biomejs/biome/issues/4751) by checking fragments inside `JSXElement` and conditional expressions. For example:
+
+The Case:
+
+```jsx
+<section>
+  <>
+    <div />
+    <div />
+  </>
+</section>;
+```
+
+And:
+
+```jsx
+showFullName ? <>{fullName}</> : <>{firstName}</>;
+```
+
+It will report.

.changeset/fix_no_fallthrough_switch_case_panic.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+The rule `noFallthroughSwitchCase` no longer panics on some incomplete code snippets.

.changeset/fix_nomissingvarfunction_false_positives_for_container_name.md

@@ -0,0 +1,5 @@
+---
+"@biomejs/biome": patch
+---
+
+Fix [#5007](https://github.com/biomejs/biome/issues/5007) `noMissingVarFunction` false positives for `container-name`.

.changeset/fix_the_use_strict_directive_insertion_logic_for_shebang_and_top_leading_comments.md

@@ -0,0 +1,47 @@
+---
+"@biomejs/biome": patch
+---
+
+Fix [#4841](https://github.com/biomejs/biome/issues/4841), shebang and top leading comments in cjs files are now handled correctly
+
+- shebang only (keep it as is)
+
+```
+#!/usr/bin/env node
+```
+
+- comments only (keep it as is)
+
+```
+// comment
+```
+
+- with shebang
+
+```diff
+- #!/usr/bin/env node"use strict";
++ #!/usr/bin/env node
++ "use strict";
+let some_variable = "some value";
+```
+
+- with comment
+
+```diff
+- // comment
+- "use strict"; // comment
++ "use strict";
++ // comment
+let some_variable = "some value";
+```
+
+- with shebang and comment
+
+```diff
+- #!/usr/bin/env node"use strict";
+- // comment
++ #!/usr/bin/env node
++ "use strict";
++ // comment
+let some_variable = "some value";
+```