v2.3.4

Compare Source

Patch Changes

• #​79894855c4a Thanks@​alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings likeconst test = "//";.
  For example, the following Astro frontmatter now parses correctly:

  ---const test="// not a real comment";---

• #​79680b28f5f Thanks@​denbezrukov! - Refactored formatter to use strictToken element for better performance. The newToken variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:

  • ASCII only (no Unicode characters)
  • No newlines (\n,\r)
  • No tab characters (\t)

  This enables faster printing and fitting logic by using bulk string operations (push_str,len()) instead of character-by-character iteration with Unicode width calculations.

• #​794119b8280 Thanks@​Conaclos! - Fixed#​7943. Rules'options are now properly merged with the inheritedoptions from a shared configuration.

  This means that you can now override a specific option from a rule without resetting the other options to their default.

  Given the following shared configuration:

  {"linter": {"rules": {"style": {"useNamingConvention": {"level":"on","options": {"strictCase":false,"conventions": [              {"selector": {"kind":"variable","scope":"global" },"formats": ["CONSTANT_CASE"]              }            ]          }        }      }    }  }}

  And the user configuration that extends this shared configuration:

  {"extends": ["shared.json"],"linter": {"rules": {"style": {"useNamingConvention": {"level":"on","options": {"strictCase":true }        }      }    }  }}

  The obtained merged configuration is now as follows:

  {"extends": ["shared.json"],"linter": {"rules": {"style": {"useNamingConvention": {"level":"on","options": {"strictCase":true,"conventions": [              {"selector": {"kind":"variable","scope":"global" },"formats": ["CONSTANT_CASE"]              }            ]          }        }      }    }  }}

• #​7969425963d Thanks@​ematipico! - Added support for the Svelte syntax{@​debug}. The Biome HTML parser is now able to parse and format the blocks:

  -{@​debug     foo,bar,    something}+{@​debug foo, bar, something}

• #​79863256f82 Thanks@​lisiur! - Fixed#​7981. Now Biome correctly detects and parseslang='tsx' andlang='jsx' languages when used inside in.vue files, when.experimentalFullSupportEnabled is enabled.

• #​7921547c2da Thanks@​dyc3! - Fixed#​7854: The CSS parser, withtailwindDirectives enabled, will now parse@source inline("underline");.

• #​7856c9e20c3 Thanks@​Netail! - Added the nursery rulenoContinue. Disallowing the usage of thecontinue statement, structured control flow statements such asif should be used instead.

  Invalid:

  letsum=0,i;for(i=0;i<10;i++){if(i>=5){continue;}sum+=i;}

  Valid:

  letsum=0,i;for(i=0;i<10;i++){if(i<5){sum+=i;}}

v2.3.3

Compare Source

Patch Changes

• #​790757bd662 Thanks@​ematipico! - Fixed#​7839. Now the Biome parser correctly parses the Astro frontmatter even when a triple fence is inside quotes.

• #​7934a35c496 Thanks@​alissonlauffer! - Fixed#​7919: The HTML parser now correctly handles Unicode BOM (Byte Order Mark) characters at the beginning of HTML files, ensuring proper parsing and tokenization.

• #​7869c80361d Thanks@​matanshavit! - Fixed#​7864: Biome now preserves component tag name casing in Svelte, Astro, and Vue files.

• #​792669cecec Thanks@​matanshavit! - Added the rulenoParametersOnlyUsedInRecursion.

  This rule detects function parameters that are exclusively used in recursive calls and can be removed to simplify the function signature since they are effectively unused.

  functionfactorial(n,acc){if(n===0)return1;returnfactorial(n-1,acc);// acc is only used here}

  Fixes#​6484.

• #​77742509b91 Thanks@​dibashthapa! - Fixed#​7657: Added the new ruleno-unknown-property from ESLint

• #​79187165d06 Thanks@​dyc3! - Fixed#​7913: The CSS parser, withtailwindDirectives enabled, will now correctly handle@slot.

• #​7959ffae203 Thanks@​siketyan! - Fixed the Biome Language Server so it no longer returns an internal error when the formatter is disabled in the configuration.

v2.3.2

Compare Source

Patch Changes

• #​7859c600618 Thanks@​Netail! - Added the nursery rulenoIncrementDecrement, disallows the usage of the unary operators ++ and --.

• #​79010d17b05 Thanks@​ematipico! - Fixed#​7837, where Biome couldn't properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.

• #​7874e617d36 Thanks@​Bertie690! - Fixed#​7230:noUselessStringConcat no longer emits false positives for multi-line strings with leading+ operators.

  Previously, the rule did not check for leading newlines on the+ operator, emitting false positives if one occurred at the start of a line.
  Notably, formatting withoperatorLinebreak="before" would move the+ operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

  Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting ofoperatorLinebreak.

  Example

  // The following code used to error if the `+` operators were at the start of lines (as opposed to the end).// Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.constreallyLongStringThatShouldNotError="Lorem ipsum dolor sit amet consectetur adipiscing elit."+"Quisque faucibus ex sapien vitae pellentesque sem placerat."+"In id cursus mi pretium tellus duis convallis."+"Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";

• #​778633ffcd5 Thanks@​daivinhtran! - Fixed#​7601: Properly match Grit plugin's code snippet with only one child.

• #​79010d17b05 Thanks@​ematipico! - Fixed#​7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

v2.3.1

Compare Source

Patch Changes

• #​784072afdfa Thanks@​ematipico! - Fixed#​7838, which caused the new--css-parse-* arguments not being recognised by theci command.

• #​7789d5b416e Thanks@​fronterior! - Fixed the LSP methodworkspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.

• #​7852bd254c7 Thanks@​dyc3! - Fixed#​7843: The CSS parser, whentailwindDirectives is enabled, correctly parses--*: initial;.

• #​78720fe13fe Thanks@​dyc3! - Fixed#​7861: The HTML parser will now accept Svelte attribute shorthand syntax in.svelte files.

• #​78667b2600b Thanks@​dyc3! - Fixed#​7860: The css parser, withtailwindDirectives enabled, will now accept@plugin options.

• #​7853fe90c78 Thanks@​dyc3! - Fixed#​7848: The css parser withtailwindDirectives enabled will now correctly parse tailwind's source exclude syntax:@source not "foo.css";

• #​7878c9f7fe5 Thanks@​ematipico! - Fixed#​7857: Biome now parses<script> tags as TypeScript when analysing.astro files.

• #​7867b42b718 Thanks@​smorimoto! - Fixed incorrect option name in HTML parser error message.

  The error message for disabled text expressions incorrectly referred
  to thehtml.parser.textExpression option, which does not exist.
  Updated it to reference the correcthtml.parser.interpolation option.

v2.3.0

Compare Source

Minor Changes

• #​7263a3e3369 Thanks@​arendjr! - Biome's resolver now supportsbaseUrl if specified intsconfig.json.

Example

Given the following file structure:

tsconfig.json

{"compilerOptions": {"baseUrl":"./src"  }}

src/foo.ts

exportfunctionfoo(){}

In this scenario,import { foo } from "foo"; should work regardless of the
location of the file containing theimport statement.

Fixes#​6432.

• #​77456fcbc07 Thanks@​dyc3! - Addedignore option tonoUnknownAtRules. If an unknown at-rule matches any of the items provided inignore, a diagnostic won't be emitted.

• #​775363cb7ff Thanks@​ematipico! - Enhanced theinit command. Theinit 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 tobiome.json:

  {+  "vcs": {+    "enabled": true,+    "clientKind": "git",+    "useIgnoreFile": true+  }}

  If Biome finds adist/ folder, it will exclude it automatically using the double-exclude syntax:

  {+  "files": {+    "includes": ["**", "!!**/dist"]+  }}

• #​754885d3a3a Thanks@​siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

• #​7723d3aac63 Thanks@​ematipico! - 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:

  biome check --css-parse-css-modules=true file.module.cssbiome format --css-parse-css-modules=true file.module.cssbiome lint --css-parse-css-modules=true file.module.cssbiome ci --css-parse-css-modules=true file.module.css

• #​7723d3aac63 Thanks@​ematipico! - 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:

  biome check --css-parse-tailwind-directives=true file.cssbiome format --css-parse-tailwind-directives=true file.cssbiome lint --css-parse-tailwind-directives=true file.cssbiome ci --css-parse-tailwind-directives=true file.css

• #​7330272632f Thanks@​ematipico! - Updated the formatting of.svelte and.vue files. Now the indentation of the JavaScript blocks matches Prettier's:

  <script>- import Component from "./Component"+   import Component from "./Component"</script>

• #​7333de0d2d6 Thanks@​dyc3! - Implemented theindentScriptAndStyle option for vue and svelte files, with the default set tofalse to matchPrettier'svueIndentScriptAndStyle option. 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:

  {"html": {"formatter": {"indentScriptAndStyle":true    }  }}

  Which will format this code to:

  <script>importComponentfrom"./Component.vue";</script>

• #​7359ebbddc4 Thanks@​arendjr! - Deprecated the optionfiles.experimentalScannerIgnores in favour offorce-ignore syntax infiles.includes.

  files.includes supports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supportsforce-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 nestedbiome.json files.

Example

Let's take the following configuration:

{"files": {"includes": ["**","!**/generated","!!**/dist","fixtures/example/dist/*.js"    ]  },"linter": {"domains": {"project":"all"    }  }}

This configuration achieves the following:

• Because theproject domain is enabled, all supported files in the project are indexedand processed by the linter,except:
• Files inside agenerated folder are not processed by the linter, but they will get indexedif a file outside agenerated folder imports them.
• Files inside adist folder are never indexed nor processed, not even if they are imported for any purpose,except:
• When thedist folder is insidefixtures/example/, its.js filesdo get both indexed and processed.

In general, we now recommend using the force-ignore syntax for any folders that containoutput files, such asbuild/ anddist/. 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 thebiome migrate --write command to automatically update the configuration file.

• #​76983b6f5e3 Thanks@​ematipico! - Added a new reporter namedrdjson. This reporter prints diagnostics following theRDJSON format:

  The following command:

  biome check --reporter=rdjson

  Will emit diagnostics in the following format:

  {"source": {"name":"Biome","url":"https://biomejs.dev"  },"diagnostics": [    {"code": {"url":"https://biomejs.dev/linter/rules/no-unused-imports","value":"lint/correctness/noUnusedImports"      },"location": {"path":"index.ts","range": {"end": {"column":11,"line":0          },"start": {"column":7,"line":0          }        }      },"message":"This import is unused."    },    {"code": {"url":"https://biomejs.dev/linter/rules/no-unused-imports","value":"lint/correctness/noUnusedImports"      },"location": {"path":"index.ts","range": {"end": {"column":10,"line":1          },"start": {"column":9,"line":1          }        }      },"message":"Several of these imports are unused."    }  ]}

• #​7719188a767 Thanks@​cadunass! - TheformatWithErrors option can now be set via CLI using the--format-with-errors flag.

  This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.

Example

biome format --format-with-errors=true --write file.js

• #​7723d3aac63 Thanks@​ematipico! - Added--json-parse-allow-comments CLI flag to control whether comments are allowed in JSON files.

  You can now enable or disable comment parsing in JSON files directly from the command line:

  biome check --json-parse-allow-comments=true file.jsonbiome format --json-parse-allow-comments=true file.jsonbiome lint --json-parse-allow-comments=true file.jsonbiome ci --json-parse-allow-comments=true file.json

• #​7723d3aac63 Thanks@​ematipico! - Added--json-parse-allow-trailing-commas CLI flag to control whether trailing commas are allowed in JSON files.

  You can now enable or disable trailing comma parsing in JSON files directly from the command line:

  biome check --json-parse-allow-trailing-commas=true file.jsonbiome format --json-parse-allow-trailing-commas=true file.jsonbiome lint --json-parse-allow-trailing-commas=true file.jsonbiome ci --json-parse-allow-trailing-commas=true file.json

• #​7758cea002f Thanks@​ematipico! - Promoted new lint rules:

  • PromotednoNonNullAssertedOptionalChain to the suspicious group
  • PromoteduseReactFunctionComponents to thestyle group
  • PromoteduseImageSize to thecorrectness group
  • PromoteduseConsistentTypeDefinitions to thestyle group
  • PromoteduseQwikClasslist to thecorrectness group
  • PromotednoSecrets to thesecurity group

  Removed the lint ruleuseAnchorHref, because its use case is covered byuseValidAnchor.

• #​6356296627d Thanks@​wrick17! - Added the newcheckstyle reporter. When--reporter=checkstyle is passed to the CLI, Biome will emit diagnostics forCheckstyle format:

  <?xml version="1.0" encoding="utf-8"?><checkstyleversion="4.3">  <filename="index.ts">    <errorline="1"column="8"severity="warning"message="This import is unused."source="lint/correctness/noUnusedImports" />    <errorline="2"column="10"severity="warning"message="Several of these imports are unused."source="lint/correctness/noUnusedImports" />    <errorline="8"column="5"severity="warning"message="This variable f is unused."source="lint/correctness/noUnusedVariables" />    <errorline="9"column="7"severity="warning"message="This variable f is unused."source="lint/correctness/noUnusedVariables" />    <errorline="1"column="1"severity="error"message="The imports and exports are not sorted."source="assist/source/organizeImports" />    <errorline="4"column="3"severity="error"message="Using == may be unsafe if you are relying on type coercion."source="lint/suspicious/noDoubleEquals" />    <errorline="6"column="1"severity="error"message="This is an unexpected use of the debugger statement."source="lint/suspicious/noDebugger" />    <errorline="8"column="5"severity="error"message="This variable implicitly has the any type."source="lint/suspicious/noImplicitAnyLet" />    <errorline="9"column="7"severity="error"message="This variable implicitly has the any type."source="lint/suspicious/noImplicitAnyLet" />    <errorline="2"column="10"severity="error"message="Shouldn&apos;t redeclare&apos;z&apos;. Consider to delete it or rename it."source="lint/suspicious/noRedeclare" />    <errorline="9"column="7"severity="error"message="Shouldn&apos;t redeclare&apos;f&apos;. Consider to delete it or rename it."source="lint/suspicious/noRedeclare" />    <errorline="0"column="0"severity="error"message="Formatter would have printed the following content:"source="format" />  </file>  <filename="main.ts">    <errorline="1"column="8"severity="warning"message="This import is unused."source="lint/correctness/noUnusedImports" />    <errorline="2"column="10"severity="warning"message="Several of these imports are unused."source="lint/correctness/noUnusedImports" />    <errorline="8"column="5"severity="warning"message="This variable f is unused."source="lint/correctness/noUnusedVariables" />    <errorline="9"column="7"severity="warning"message="This variable f is unused."source="lint/correctness/noUnusedVariables" />    <errorline="1"column="1"severity="error"message="The imports and exports are not sorted."source="assist/source/organizeImports" />    <errorline="4"column="3"severity="error"message="Using == may be unsafe if you are relying on type coercion."source="lint/suspicious/noDoubleEquals" />    <errorline="6"column="1"severity="error"message="This is an unexpected use of the debugger statement."source="lint/suspicious/noDebugger" />    <errorline="8"column="5"severity="error"message="This variable implicitly has the any type."source="lint/suspicious/noImplicitAnyLet" />    <errorline="9"column="7"severity="error"message="This variable implicitly has the any type."source="lint/suspicious/noImplicitAnyLet" />    <errorline="2"column="10"severity="error"message="Shouldn&apos;t redeclare&apos;z&apos;. Consider to delete it or rename it."source="lint/suspicious/noRedeclare" />    <errorline="9"column="7"severity="error"message="Shouldn&apos;t redeclare&apos;f&apos;. Consider to delete it or rename it."source="lint/suspicious/noRedeclare" />    <errorline="0"column="0"severity="error"message="Formatter would have printed the following content:"source="format" />  </file></checkstyle>

• #​7488b13e524 Thanks@​kpapa05! - Added "@​rbxts/react" as an alias for "react" for handling the reactClassic jsxRuntime.

• #​75360bccd34 Thanks@​TheAlexLichter! - Added.oxlintrc.json to well-known files.

• #​754885d3a3a Thanks@​siketyan! - The following rules are now a part of thereact domain, and they won't be enabled automatically unless you enabled the domain, or Biome detectsreact as a dependency of your closestpackage.json:

  • lint/correctness/noChildrenProp (recommended)
  • lint/correctness/noReactPropAssignments
  • lint/security/noDangerouslySetInnerHtml (recommended)
  • lint/security/noDangerouslySetInnerHtmlWithChildren (recommended)
  • lint/style/useComponentExportOnlyModules
  • lint/suspicious/noArrayIndexKey (recommended)

• #​7667480909a Thanks@​ematipico! - Added the ability to show severityInformation diagnostics in reporter outputs.

  If one or more rules are triggered, and they are configured to emit anInformation diagnostic, now they're counted in the final output:

  Checked 1 filein<TIME>. No fixes applied.Found 1 info.

• #​770228e8860 Thanks@​ematipico! - Added linting and assist support for.html files, with addition of two new configurations:

  • html.linter.enabled
  • html.assist.enabled

  The HTML linter, in this release, only contains the rulenoHeaderScope. More rules will be released in the upcoming releases.

• #​7164f66b0c5 Thanks@​dyc3! - Added a new CSS parser optiontailwindDirectives. Enabling this option will allow all of Tailwind v4's syntax additions to be parsed and formatted by Biome.

  You can enable this by settingcss.parser.tailwindDirectives totrue in your Biome configuration.

  {"css": {"parser": {"tailwindDirectives":true    }  }}

• #​76696ed4d16 Thanks@​barklund! - React 19.2 support is now supported in Biome:

  • TreatsuseEffectEvent likeuseRef inuseExhaustiveDependencies
  • Added<Activity /> to known React APIs.

• #​770228e8860 Thanks@​ematipico! - Addedexperimental full support for HTML, Vue, Svelte and Astro files. In this release, the HTML parser
  has been enhanced, and it's now able to parse.vue,.svelte and.astro files.

  This means that now Biome is able to lint and format the JavaScript (TypeScript), HTML and CSS code that is contained in these files.

  Now that the main architecture is stable and working, in the upcoming patches and minors we will also fix possible inaccuracies and edge cases coming from existing lint rules, such asnoUnusedVariables inside<script> blocks or frontmatter.

  The support is considered experimental because there might be cases that aren't fine-parsed yet, hence causing possible inaccuracies when it comes to formatting and linting.

• #​759909445c8 Thanks@​anaisbetts! - #### lineEnding has a new optionauto

  The optionlineEnding now has a variant calledauto to match the operating system's expected
  line-ending style: on Windows, this will be CRLF (\r\n), and on macOS / Linux, this will
  be LF (\n).

  This allows for cross-platform projects that use Biome not to have to
  force one option or the other, which aligns better with Git's default behavior
  on these platforms.

  Example usage:

  {"formatter": {"lineEnding":"auto"  }}

  biome format --line-ending auto

• #​7392e4feb8e Thanks@​ematipico! - Added new capabilities to the CLI arguments--skip and--only, available to thebiome lint command.

  --skip and--only can now accept domain names; when provided, Biome will run or skip all the rules that belong to a certain domain.

  For example, the following command will only run the rules that belong to thenext domain:

  biome lint --only=next

  Another example, the following command will skip the rules that belong to theproject domain:

  biome lint --skip=project

• #​770228e8860 Thanks@​ematipico! - Added a new option calledhtml.interpolation. This option enables the parsing of text expressions (or interpolation) in HTML files.

  The followingfile.html will be correctly formatted:

  <!-- file.html --><div>  Hello {{ name }}!<p>Your balance is: {{ account.balance }}</p><button>{{ isLoading ? "Loading..." : "Submit" }}</button></div>

  To note thathtml.interpolation only parses text expressions that are delimited by double curly braces ({{ }}). The content of expressions is parsed as normal text.

Patch Changes

• #​7712fcc9b42 Thanks@​minht11! - Added new ruleuseVueDefineMacrosOrder which allows enforcing specific order for Vue compiler macros.

  In this example, the rule will suggest movingdefineProps beforedefineEmits:

  <script lang="ts" setup>const emit=defineEmits(["update"]);const props=defineProps<{ name:string }>();</script>

• #​76983b6f5e3 Thanks@​ematipico! - Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.

• #​7819ef45056 Thanks@​ematipico! - Fixed#​7788. Removes some error logging that were emitted when loading possible configuration files.

• #​7593e51dd55 Thanks@​arendjr! - Fixed an issue with thefiles.maxSize setting. Previously the setting would always be looked up in the root settings, even in monorepos where a closerbiome.json is available. It now correctly uses the nearest configuration.

• #​7825ad55b35 Thanks@​Conaclos! - Fixed#​7798.useNamingConvention no longer panics when it encounters a name that consists of a single dollar sign$ that doesn't match a custom convention.

• #​776493be2ab Thanks@​gaauwe! - Fixed#​6589: Biome now properly loads extension settings before loading the configuration file when opening a text document in the LSP server.

v2.2.7

Compare Source

Patch Changes

• #​7715b622425 Thanks@​Netail! - Added the nursery rulenoEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter.

• #​7714c7e5a14 Thanks@​MeGaNeKoS! - Increased the maximum line limit fornoExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components.

• #​58682db73ae Thanks@​bushuai! - Fixed#​5856,noRedundantUseStrict now keeps leading trivia

• #​7756d665c97 Thanks@​ematipico! - Improved the diagnostic message of the rulenoDuplicateTestHooks.

v2.2.6

Compare Source

Patch Changes

• #​7071a8e7301 Thanks@​ptkagori! - Added theuseQwikMethodUsage lint rule for the Qwik domain.

  This rule validates Qwik hook usage. Identifiers matchinguseXxx must be called only within serialisable reactive contexts (for example, insidecomponent$, route loaders/actions, or within other Qwik hooks), preventing common Qwik antipatterns.

  Invalid:

  // Top-level hook call is invalid.conststate=useStore({count:0});functionhelper(){// Calling a hook in a non-reactive function is invalid.constloc=useLocation();}

  Valid:

  component$(()=>{conststate=useStore({count:0});// OK inside component$.return<div>{state.count}</div>;});consthandler=$(()=>{constloc=useLocation();// OK inside a $-wrapped closure.console.log(loc.params);});

• #​768552071f5 Thanks@​denbezrukov! - Fixed#​6981: TheNoUnknownPseudoClass rule no longer reports local pseudo-classes when CSS Modules are used.

• #​7640899f7b2 Thanks@​arendjr! - Fixed#​7638:useImportExtensions no longer emits diagnostics on valid import paths that end with a query or hash.

Example

// This no longer warns if `index.css` exists:importstylefrom"../theme/index.css?inline";

• #​7071a8e7301 Thanks@​ptkagori! - Added theuseQwikValidLexicalScope rule to the Qwik domain.

  This rule helps you avoid common bugs in Qwik components by checking that your variables and functions are declared in the correct place.

  Invalid:

  // Invalid: state defined outside the component's lexical scope.letstate=useStore({count:0});constComponent=component$(()=>{return(<buttononClick$={()=>state.count++}>Invalid:{state.count}</button>);});

  Valid:

  // Valid: state initialised within the component's lexical scope and captured by the event.constComponent=component$(()=>{conststate=useStore({count:0});return<buttononClick$={()=>state.count++}>Valid:{state.count}</button>;});

• #​76205beb1ee Thanks@​Netail! - Added the ruleuseDeprecatedDate, which makes a deprecation date required for the graphql@deprecated directive.

  Invalid

  query {member @​deprecated(reason: "Use `members` instead") {id  }}

  Valid

  query {member    @​deprecated(reason: "Use `members` instead", deletionDate: "2099-12-25") {id  }}

• #​7709d6da4d5 Thanks@​siketyan! - Fixed#​7704: TheuseExhaustiveDependencies rule now correctly adds an object dependency when its method is called within the closure.

  For example:

  functionComponent(props){useEffect(()=>{props.foo();},[]);}

  will now be fixed to:

  functionComponent(props){useEffect(()=>{props.foo();},[props]);}

• #​7624309ae41 Thanks@​lucasweng! - Fixed#​7595:noUselessEscapeInString no longer reports$\{ escape in template literals.

• #​766529e4229 Thanks@​ryan-m-walker! - Fixed#​7619: Added support for parsing the CSS:state() pseudo-class.

  custom-selector:state(checked) {}

• #​760841df59b Thanks@​ritoban23! - Fixed#​7604: theuseMaxParams rule now highlights parameter lists instead of entire function bodies. This provides more precise error highlighting. Previously, the entire function was highlighted; now only the parameter list is highlighted, such as(a, b, c, d, e, f, g, h).

• #​7643459a6ac Thanks@​daivinhtran! - Fixed#​7580: Include plugin in summary report

v2.2.5

Compare Source

Patch Changes

• #​75975c3d542 Thanks@​arendjr! - Fixed#​6432:useImportExtensions now works correctly with aliased paths.

• #​7269f18dac1 Thanks@​CDGardner! - Fixed#​6648, where Biome'snoUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under thenoUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>,<React.Fragment>B</React.Fragment>,<RenamedFragment>B</RenamedFragment>) would not havenoUselessFragments emitted for them.

  On the Biome side, instances such as these would emitnoUselessFragments, and applying the suggest