NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3182 most downloaded on npm
Latest stable
2.6.7
Last release 6 days ago
11 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
155 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
…, "plugins" : { "rules" : [ "@org/shared-rules/noDeprecatedApi" , "@org/strict-rules/presets/recommended" , { "useCompanyLogger" : "./rules/useCompany…
#11479 5c60ba8 Thanks @nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.
#11742 3a1356d Thanks @Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.
#12318 774b5b5 Thanks @Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.
Invalid:
type User {
id: ID!
}
enum Role {
ADMIN
USER
}
directive @auth on FIELD_DEFINITION#6886 3479d15 Thanks @christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.
#11102 0874b7f Thanks @gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.
#10711 40de5a0 Thanks @soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.
This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.
{
"plugins": [
{ "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
{ "path": "local-plugin.grit", "resolutionKind": "project" },
{ "path": "local-plugin.grit" }
]
}Use resolutionKind: "config" to resolve the plugin from the configuration file that declares it. Use resolutionKind: "project" to resolve the plugin from the consuming project. When omitted, resolutionKind defaults to project. This only affects plugin resolution; includes still apply to end-user project files as usual.
#11432 4befd08 Thanks @ematipico! - Added biome inspect config to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.
Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.
#11477 ab05554 Thanks @nhedger! - Added automatic Git VCS integration when running biome init inside a Git repository, including from nested directories and Git worktrees. The generated configuration sets vcs.enabled and vcs.useIgnoreFile to true, with vcs.clientKind set to "git".
#11451 1ac4b09 Thanks @ematipico! - #### YAML is now supported
Added support for formatting YAML files, both .yaml and .yml extensions
#11432 4befd08 Thanks @ematipico! - Configuration files can now recursively extend local files and npm package configurations up to ten levels. Every repeated reference participates in the merge, while resolving multiple versions of one extended package produces an error.
#11713 ac6a640 Thanks @dyc3! - Added support for Grit range() patterns, addressing #8454. Plugins can filter syntax nodes by optional start_line, start_column, end_line, and end_column bounds.
For example, this pattern matches function calls contained entirely on line 2.
range(start_line=2, end_line=2) as $call where {
$call <: call_expression()
}
#11244 0628b53 Thanks @ematipico! - Added the new CLI option --profile-type-inference to the commands lint and check.
The profiler is designed to track the execution time of internal queries and operations, group them by file, and sort them from the most expensive to the least expensive.
biome lint --profile-type-inferenceprofiler ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
i Type inference profile (Biome <version>)
src/index.ts
Requests (top 5 of 12 groups; 28 source records; 46 executions)
1. Promise classification <- nursery/noFloatingPromises
...
Queries (top 8 of 25 groups; 61 source records; 94 executions)
1. Promises / infer_expression_is_promise
...
Whole-module inference (top 1 of 1 group; 1 source record; 1 execution)
1. Import depth limit
...
68 files omitted.
ℹ To show all the information, use the --verbose option. The output might be very verbose, so it's advised to analyze a single file.
$ biome lint --profile-type-inference --verbose ./path/to/file.ts
Use --verbose to include detailed timings, attribution, breadth, and implementation references for the top source records in each file.
#12108 4fcb880 Thanks @ematipico! - Promoted 59 nursery rules to stable groups.
Promoted the following rules to the correctness group with error severity. All of them are recommended:
noDuplicateFieldDefinitionNamesnoVueRefAsOperandnoVueImportCompilerMacrosnoVueVOnNumberValuesuseVueValidVFornoComponentHookFactoriesnoJsxNamespaceuseReactAsyncServerFunctionnoReactNativeRawTextuseReactNativePlatformComponentsuseQwikLoaderLocationnoPlaywrightMissingAwaitusePlaywrightValidDescribeCallbackPromoted the following rules to the suspicious group:
noLoopFuncnoJsxLeakedDollarnoReactStringRefs (recommended)useScopedStyles (recommended)noReactNativeDeepImports (recommended, error severity)noDrizzleDeleteWithoutWhere (recommended, error severity)noDrizzleUpdateWithoutWhere (recommended, error severity)noConditionalExpectuseExpectnoIdenticalTestTitle (recommended)noPlaywrightForceOptionnoPlaywrightNetworkidlenoPlaywrightPagePausenoPlaywrightWaitForNavigationnoPlaywrightWaitForTimeoutnoDuplicateSelectorsnoEmptyObjectKeysuseBaselinenoUntrustedLicensesPromoted useIframeSandbox to the security group with error severity.
Promoted the recommended rule useDomNodeTextContent to the performance group with warning severity.
Promoted the following rules to the complexity group:
useArraySomeuseRegexpTestnoUnnecessaryTemplateExpressionnoPlaywrightUselessAwaitnoExcessiveSelectorClassesuseMathMinMax (recommended, warning severity)noExcessiveNestedCallbacksPromoted the following rules to the style group with information severity:
useVueConsistentDefinePropsDeclarationuseVueNextTickPromise (recommended)noReactNativeLiteralColorsuseConsistentTestItuseTestHooksInOrderuseTestHooksOnTopnoPlaywrightEvalnoPlaywrightElementHandlenoPlaywrightWaitForSelectoruseReduceTypeParameteruseNamedCaptureGroupuseUnicodeRegexuseImportsFirstuseVarsOnTopuseThisInClassMethodsnoInlineStylesuseDomQuerySelectornoTopLevelLiterals#12206 0f984fb Thanks @dyc3! - Added the ignoreUsingDeclarations option to noUnusedVariables. When enabled, the rule no longer reports unused variables declared with using or await using, because these declarations clean up their value automatically even when the code never reads it.
{
"linter": {
"rules": {
"correctness": {
"noUnusedVariables": {
"options": { "ignoreUsingDeclarations": true }
}
}
}
}
}#12424 6a41490 Thanks @siketyan! - Removed the javascript.parser.gritMetavariables option. It was intended for internal use only and had no effect on how Biome parses JavaScript and TypeScript files. Biome now reports it as an unknown key and exits with a configuration error, so remove it from your configuration file.
#12055 54870c0 Thanks @ff1451! - Added the new assist action useGraphqlSortedVariables, which sorts the variable definitions of GraphQL operations.
Invalid:
query GetUser($userId: ID!, $includePosts: Boolean = false, $after: String) {
user(id: $userId) {
name
}
}#12149 83df808 Thanks @dyc3! - Added the tailwind.stylesheet option, which points Biome at the CSS file that holds your Tailwind CSS configuration. useTailwindSortedClasses reads the @theme, @utility, and @custom-variant rules in that file and in the local files it imports, so your own theme values, utilities, and variants sort correctly.
// biome.json
{
"tailwind": { "stylesheet": "./src/app.css" }
}/* src/app.css */
@import "tailwindcss";
@theme {
--color-brand: #3b82f6;
}
@utility content-auto {
content-visibility: auto;
}
@custom-variant theme-midnight (&:where([data-theme="midnight"] *));#12206 0f984fb Thanks @dyc3! - Added migration of the ignoreRestSiblings and ignoreUsingDeclarations options of no-unused-vars, @typescript-eslint/no-unused-vars, and unused-imports/no-unused-vars to noUnusedVariables in biome migrate eslint. Options that the ESLint configuration omits are set to ESLint's defaults, so the migrated rule reports the same variables. For example, "no-unused-vars": "error" now migrates ignoreRestSiblings as false.
#11709 32d12cb Thanks @ematipico! - Added the new command biome inspect file, which returns developer information for the given file.
biome inspect file path/to/file.tsBy default, the command returns the CST of the file. The command accepts the following arguments:
--ast, which returns the AST of a file.--ir, which returns the formatting IR of a file.--semantic, which returns the semantic model information of a file, if available.#12221 cb571af Thanks @dyc3! - The rule noEmptySource now supports Markdown files. It reports files that contain only blank lines and HTML comments. For example, the following file is now reported:
<!-- TODO -->#12214 8955b56 Thanks @dyc3! - The rule noEmptySource now supports YAML files. It reports files with no documents and each document that has no content. For example, the second document in the following code is now reported:
name: foo
---#12033 8669e53 Thanks @dyc3! - Added the ignoreElements option to noRedundantRoles. Elements listed in this option are not checked by the rule.
{
"linter": {
"rules": {
"a11y": {
"noRedundantRoles": {
"options": {
"ignoreElements": ["button"]
}
}
}
}
}
}#12084 04e3750 Thanks @dyc3! - The rule noRestrictedElements now supports HTML, Vue, Svelte, and Astro files. For example, with { "elements": { "marquee": "Use CSS animations instead." } }, the following code is now reported:
<marquee>Breaking news</marquee>#11408 5a870f2 Thanks @ematipico! - Added support for distributing named Grit rules, rule presets, and configurations through packages that have a manifest file.
The field plugins is used to export named Grit plugins, and configs is used to export named configurations.
Package entries must select a named export: package/rule, package/presets/preset, or package/configs/config. Bare package entries aren't supported.
Rules consumed from another package are exposed under the consuming package's name, while package authors continue to reference them by their source package inside the manifest.
Configurations consumed from another package are also exposed under the consuming package's name.
// biome-manifest.json
{
"$schema": "./node_modules/@biomejs/biome/manifest_schema.json",
"version": 1,
"plugins": {
"rules": [
"@org/shared-rules/noDeprecatedApi",
"@org/strict-rules/presets/recommended",
{ "useCompanyLogger": "./rules/useCompanyLogger.grit" }
],
"presets": {
"recommended": [
"useCompanyLogger",
"@org/shared-rules/noDeprecatedApi"
]
}
},
"configs": [
"@org/shared-configs/configs/recommended",
{ "base": "./configs/base.json" }
]
}The package must publish the manifest and every referenced file, for example, through the files field in package.json.
Plugin authors can expose their manifest through the biome condition with ./biome-manifest.json as its value.
// package.json
{
"name": "@org/biome-plugin",
"exports": {
"biome": "./biome-manifest.json",
"default": "./index.js"
},
"files": ["biome-manifest.json", "rules", "configs"]
}And then, you can load the rules in your biome.json:
// biome.json
{
"plugins": [
"@org/biome-plugin/useCompanyLogger",
"@org/biome-plugin/presets/recommended"
]
}For more information on how to create a plugin to distribute via npm, check the relative guide.
#12264 90f2eaf Thanks @dyc3! - Fixed #11082: glob patterns in the includes option of a plugin are now matched against file paths relative to the directory of the configuration file, the same as files.includes and overrides[].includes.
Previously, the patterns were matched against the absolute file path, so a pattern such as packages/**/src/** matched no files and the plugin never ran.
{
"plugins": [
{ "path": "./my-plugin.grit", "includes": ["packages/**/src/**"] }
]
}Patterns that start with **/ keep working. Patterns that contain the absolute path of the project no longer match, and must be rewritten as relative patterns.
#11133 1df00de Thanks @dlecan! - Added Android (Termux) support to the npm distribution (#1340). npm install @biomejs/biome now works on Termux through the new @biomejs/cli-android-arm64 and @biomejs/cli-android-x64 packages, which reuse the static musl binaries.
#12132 c5fadc4 Thanks @ematipico! - Added SCSS support throughout the toolchain. Biome can now format and lint .scss files, and recognizes .module.scss files as CSS Modules.
#10837 754432c Thanks @JamBalaya56562! - Added support for Google Apps Script (.gs) files.
They are parsed as JavaScript scripts, so ES module import/export statements are reported as errors (Apps Script has no module system). Common Apps Script service globals (e.g. SpreadsheetApp, DriveApp, Logger) are recognized by noUndeclaredVariables and noGlobalAssign, and the list can be extended through the javascript.globals option.
#11126 fa63050 Thanks @Punisheroot! - Biome now recognizes files with the .htm extension as HTML.
#12291 6c6619e Thanks @dyc3! - Changed the dependency that enables the tailwind domain automatically. The domain is now enabled when package.json declares tailwindcss v4 or later, instead of v3 or later, because we are currently targeting Tailwind v4 support. The domain can always be enabled manually.
#11394 de1ad4c Thanks @ematipico! - #### Markdown is now supported
Added support for linting and formatting Markdown files. The first version of Biome Markdown parser has 100% compatibility
against CommonMark.
Other variants of Markdown, such as GitHub Flavored Markdown (GFM) aren't currently supported; however, we plan to support them soon.
Formatter and Linter are automatically enabled by default.
The parser comes with an opt-in option to enable frontmatter parsing. When enabled, the first thematic break --- is considered the opening fence of the frontmatter:
// biome.json
{
"markdown": {
"parser": {
"frontmatter": true
}
}
}---
title: Lorem ipsum
---The parser also comes with an opt-in option called cjkFriendlyEmphasis. When enabled, the parser follows the CommonMark CJK-friendly amendments and recognizes emphasis markers, such as **, placed directly next to Chinese, Japanese, or Korean text. Enable it only when the tool that renders your Markdown supports the same amendments, because the option changes which text Biome formats and lints as emphasis:
// biome.json
{
"markdown": {
"parser": {
"cjkFriendlyEmphasis": true
}
}
}With the option enabled, the following text is parsed as bold, instead of as literal **:
**このアスタリスクは強調記号として認識されず、そのまま表示されます。**この文のせいで。The formatter has great compatibility with Prettier formatting, more than 90% detected by our infrastructure. The formatter ships with
a new option called proseWrap, that allows controlling how the Biome formatter should wrap paragraphs.
For example, when proseWrap is set to always, the formatter will wrap the paragraph to match the configured lineWidth:
// biome.json
{
"markdown": {
"formatter": {
"lineWidth": 20,
"proseWrap": "always"
}
}
}Very tiny line width, so
the paragraph is more
compact.The linter ships with a few rules inspired by markdownlint. We plan to ship more rules in the upcoming releases.
Some rules you can start using already:
Biome recognizes the code inside fenced code blocks, frontmatter, and HTML blocks as embedded languages, and formats it with
the formatter of its language and your configuration:
```js
-const value = {a:1,b:2}
+const value = { a: 1, b: 2 };
```HTML blocks are formatted only when the HTML formatter is enabled. A block with a syntax error stays as written, and Biome
still formats the rest of the file.
The option markdown.formatter.formatEmbeds controls this behavior, and it's enabled by default. Set it to false to keep
the code of these blocks as written:
// biome.json
{
"markdown": {
"formatter": {
"formatEmbeds": false
}
}
}The command biome migrate prettier migrates the Prettier option embeddedLanguageFormatting
to markdown.formatter.formatEmbeds.
The option markdown.analyzeEmbeds runs the linter and assist actions on the same blocks, with the rules and actions of
their language, and reports their syntax errors. It's disabled by default, because fenced code blocks usually contain
examples or partial code:
// biome.json
{
"markdown": {
"analyzeEmbeds": true
}
}#11634 04c3f5d Thanks @ematipico! - Added biome inspect plugins to list resolved rules by plugin and importing preset without loading or executing plugin code. Include globs show which files each import targets, and --path selects a target file. Fixed Markdown linter overrides and their configuration inspection.
#12282 a3fa0d6 Thanks @ff1451! - Added the new assist action useGraphqlSortedArguments, which sorts the arguments of GraphQL fields and directives, and the arguments declared by field and directive definitions.
Invalid:
query {
users(orderBy: NAME, first: 10, after: "cursor") {
name
}
}#10631 1077238 Thanks @thibaut-pro! - Added the sortFirst option to the useSortedAttributes action (JSX and HTML). It takes a list of attribute names that are sorted before all other attributes, in the order given, while the remaining attributes keep their usual sort. This is useful to keep attributes such as key first.
With the following configuration:
{
"assist": {
"actions": {
"source": {
"useSortedAttributes": {
"level": "on",
"options": { "sortFirst": ["key"] }
}
}
}
}
}The attributes are reordered so that key comes first:
// Before
<div className={styles.investment} key={investment.id} />;
// After
<div key={investment.id} className={styles.investment} />;#10424 189b7ba Thanks @LinusU! - Added the partitionByNewLine option to the useSortedInterfaceMembers assist. When enabled, members separated by a blank line are kept in their own section and sorted only within that section, preserving the logical groupings the author intentionally introduced with empty lines.
#11953 354f74c Thanks @Th3S4mur41! - Enhanced the nursery rule useLogicalProperties to check physical CSS values in addition to physical property names.
The rule recognizes physical values in frame-sizing, anchor-size(), and anchor(), with direction-aware replacements controlled by the existing direction option.
For justify-content: left and justify-content: right, the rule reports a diagnostic without an automatic replacement because the correct logical alignment depends on the layout axis.
This is a second part of the rule covering parts of #9034
#12175 3730b32 Thanks @dyc3! - Added the nursery rule noDoubleComparison, which reports two comparisons of the same values that can be combined into one. For example, x === y || x < y can be written as x <= y.
#12166 25eb10c Thanks @dyc3! - Added the new nursery rule noNestedSwitch, which disallows switch statements inside other switch statements.
switch (n) {
case 0:
switch (m) {} // reported
}#12170 872ac9f Thanks @dyc3! - Added the new nursery rule noNestedTemplateLiterals, which disallows template literals written inside other template literals.
const message = `I have ${color ? `${count} ${color}` : count} apples`;#12111 f72375f Thanks @dyc3! - Added the nursery rule noObjectConstructor, which disallows calling the Object constructor without arguments, such as new Object() or Object(). Biome can replace these calls with the object literal {}.
#12254 cb88f07 Thanks @dyc3! - Added the nursery rule noSvelteClassDirective, which reports Svelte's class: directive. Since Svelte 5.16, the class attribute accepts objects and arrays, and Svelte recommends them over the directive.
<div class:active={isActive}></div>#12186 30aa7d2 Thanks @dyc3! - Added the new nursery rule noUselessDateGetTime, which reports dates converted with .getTime() before being passed to the Date constructor. Passing the date directly, as in new Date(date), already creates a copy.
const copy = new Date(date.getTime());#12229 5f8ea6c Thanks @dyc3! - Added the nursery rule noVueLifecycleAfterAwait, which reports Vue lifecycle hooks, such as onMounted(), that are registered after an await in a component's setup() function. Vue doesn't run these hooks.
<script>
import { onMounted } from "vue";
export default {
async setup() {
await fetchUser();
onMounted(() => {});
},
};
</script>#12077 3dd096f Thanks @dyc3! - Added the nursery rule noVueRootVIf, which disallows v-if on the only root element of a Vue component template.
<template>
<div v-if="visible">Content</div>
</template>#12136 b92638b Thanks @dyc3! - Added the nursery rule noVueShadowNativeEvents, which reports Vue component events named after built-in browser events, such as click or keydown.
<script setup>
// Invalid
const emit = defineEmits(["click"]);
emit("click");
</script>#12135 31a29b6 Thanks @dyc3! - Added the nursery rule noVueVHtml, which disallows Vue's v-html directive. v-html inserts its value into the page as HTML, so text from users can run code on your page (cross-site scripting, or XSS).
<template>
<div v-html="content"></div>
</template>#12134 60329af Thanks @dyc3! - Added the new nursery rule noVueVText, which disallows Vue's v-text directive in favor of text interpolation.
For example, the following snippet triggers the rule:
<div v-text="message"></div>#9817 241b861 Thanks @dyc3! - Added the new nursery rule noZeroFractions, which disallows numeric literals with redundant zero fractions or dangling dots such as 1.0 and 1.. Biome can now simplify these literals to shorter equivalents.
#12109 b45d426 Thanks @dyc3! - Added the nursery rule useConsistentJsonFileRead, which enforces a consistent way of reading JSON files before passing them to JSON.parse(). By default, it reports files read as a Buffer; set readAs to "buffer" to report files read as a UTF-8 string instead.
const packageJson = JSON.parse(await fs.readFile("./package.json"));#12129 b57f874 Thanks @dyc3! - Added the new nursery rule useMatchingFunctionName, which requires a named function expression to have the same name as the variable or property it's assigned to.
// The function name `bar` doesn't match the variable name `foo`.
const foo = function bar() {};#12169 0f1ae53 Thanks @dyc3! - Added the new nursery rule useSimplifiedBooleanReturn, which reports if statements that only return true or false and can be replaced by returning the condition directly.
function isPositive(value) {
if (value > 0) {
return true;
}
return false;
}#11957 b2db9f2 Thanks @dyc3! - Added the nursery rule useSvelteKitResolve, which requires internal links and calls to goto(), pushState(), and replaceState() to use paths built with SvelteKit's resolve().
<a href="/about">About</a>#12235 b7c1870 Thanks @dyc3! - Added the nursery rule useSvelteReactiveClasses, which reports Date, Map, Set, URL, and UR
Note truncated.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
For example, the following snippet triggers the rule.
#10634 b436ba0 Thanks @subaru-hello! - Added the new nursery rule noReactObjectTypeAsDefaultProp, which disallows array, object, and function values as default props in React components.
For example, the following snippet triggers the rule.
function Component({ items = [] }) {
return items;
}#11956 faa8b37 Thanks @dyc3! - Added the nursery rule noSvelteExportLet, which disallows declaring Svelte component props with the legacy export let syntax. Use the $props() rune instead.
<script>
export let name;
</script>#10816 1b9479e Thanks @Th3S4mur41! - Added a new nursery rule useLogicalProperties that enforces the use of logical properties in CSS, promoting better internationalization and accessibility practices. The rule supports a direction option with "ltr" as the default and "rtl" as the alternative.
This is a first rule covering parts of #9034
{
"linter": {
"rules": {
"nursery": {
"useLogicalProperties": {
"level": "warn",
"options": {
"direction": "rtl"
}
}
}
}
}
}#11960 1fdb5c2 Thanks @dyc3! - Added the nursery rule useSvelteKitRuneImports, which reports imports from the deprecated $app/stores module and suggests $app/state instead.
import { page } from "$app/stores";#11723 3b429d1 Thanks @m1handr! - Fixed #11656: noAstroSetHtmlDirective now correctly reports set:html directives inside Astro template expressions.
#12023 874d5ae Thanks @codspeed! - Improved the performance of the HTML formatter up to 4x.
#11761 a3462fe Thanks @saberoueslati! - Fixed #11351: useSimplifiedLogicExpression no longer reports boolean literals on the right side of || and && outside boolean contexts, because removing them can change the result of the expression. For example, y = x || false is no longer reported, while if (x || false) still is.
#11732 ff4c4dd Thanks @dyc3! - Added the nursery rule noMeaninglessVoidOperator, which reports unnecessary uses of void, such as void log() when log returns void. The rule allows discarded call results, thenables, void 0, and calls returning never.
#11975 40dd3fb Thanks @ematipico! - Fixed the indentation of multiline Astro expressions, in templates and attribute values, when running biome check --write. Biome now formats Astro expressions with biome format too, and places them at the column of the surrounding markup.
<div>
{items.map((item) => (
- <span>{item}</span>
-))}
+ <span>{item}</span>
+ ))}
</div>#12016 09d4000 Thanks @codspeed! - Improved the performance of indexing and analysis of big files up to 2x. The improvements are mostly visible in projects that make use of project and types lint rules.
#11750 089bde0 Thanks @dyc3! - Added the nursery rule useStrictBooleanExpressions, which reports ambiguous truthiness checks such as if (value) when value has type number | undefined. Non-nullable strings and numbers and nullable objects are allowed; the rule has no options.
#11494 ad5b362 Thanks @jp-knj! - Added the nursery rule noAstroConflictingSetDirectives, which reports Astro elements with multiple content sources, such as set:html, set:text, and child content.
For example, <div set:html={html}>content</div> triggers the rule.
#11878 84d1b3b Thanks @dyc3! - Fixed #11748: useExhaustiveSwitchCases now reports missing cases for values created with the mapping overload of Array.from, including arrays imported from another module.
#11802 7d1f37e Thanks @dyc3! - Tailwind classes will now be detected in Svelte, Vue, and Astro class attribute expressions that don't use a class merging function.
#11910 9e50ea2 Thanks @ematipico! - Fixed #11504, a regression where Biome would silently ignore errors in the configuration file. Now errors are correctly retained and checked before executing any command.
#11921 d568632 Thanks @hirehamir! - Fixed #10846: when plugins fail to load, Biome now prints each failing plugin's path on its own line, instead of concatenating bare messages like Cannot read file.Cannot read file..
#11930 82ea5a6 Thanks @dyc3! - Fixed #11927: The HTML formatter no longer duplicates comments around Svelte blocks. This affected a comment after a block such as {#if} or {#each} at the end of an element, and a comment on the same line as the last element inside a block, before {:else}, {/if}, or a similar tag.
#11931 0cc46d8 Thanks @dyc3! - Fixed the indentation of comments at the end of a Svelte block's contents. A comment before {:else}, {:then}, {/if}, or a similar tag is now indented with the block's contents instead of with the tag.
{#if condition}
<span>Text</span>
-<!-- comment -->
+ <!-- comment -->
{/if}#12031 ef0edd4 Thanks @dyc3! - Fixed #12027: Biome's test rules no longer mistake regular method calls named test, it, or describe for tests. For example, useValidTestTitle used to report the following regular expression check as a test with an invalid title:
const isComment = /^\s*#/.test(line);#11959 8477e61 Thanks @dyc3! - Fixed #11950: noUnusedVariables now reports arrow functions with expression bodies that only reference themselves, such as let h = () => h();.
#11915 3260602 Thanks @ematipico! - Fixed #11841, where suppression comments had no effect on some parts of HTML-ish files and on snippets embedded in JavaScript files.
Now the following suppression works as expected:
<!-- biome-ignore lint/correctness/noUndeclaredVariables: intentionally external -->
<div :title="missingValue"></div>#11952 b51040e Thanks @dyc3! - Fixed #11951: the GritQL formatter no longer inserts a space after a within pattern without an until clause.
-$arg <: within `bar($_)` ,
+$arg <: within `bar($_)`,#11794 429cf95 Thanks @dyc3! - Added the nursery rule noTailwindRawColors for JavaScript and HTML. It disallows Tailwind palette colors such as bg-pink-500 and text-white, encouraging design system color utilities such as bg-primary.
#11837 f5e249b Thanks @dyc3! - Fixed #11836: biome check --write no longer adds invalid parentheses around Svelte {@const} declarations when experimental HTML support and formatting are enabled.
#11978 8be0b9e Thanks @dyc3! - Fixed #11817: Biome no longer crashes when its output is piped to a program that exits early, such as head. Output to the closed pipe is now discarded and Biome exits normally.
#11868 3841c26 Thanks @ematipico! - Fixed #8986: Biome's language server now scopes all watched-file patterns to each workspace folder, falling back to the deprecated rootUri when no workspace folders are provided. Clients without relative-pattern support receive compatible absolute glob patterns.
#11928 0015681 Thanks @dyc3! - Restricted access to the Unix daemon socket to the user running Biome. The socket now lives in a biome-daemon directory inside Biome's cache directory that only this user can access, and the socket itself has mode 0600.
#11835 589ca1a Thanks @dyc3! - Updated useReactCompiler: Biome now reports React Compiler diagnostics regardless of the React version declared in package.json.
#11907 b7d9037 Thanks @posido! - Fixed withastro/compiler-rs#194: the HTML parser no longer treats a regex literal that starts with > as the end of a self-closing tag. Astro frontmatter such as const escaped = s.replace(/>/g, ">"); no longer swallows the closing --- fence, and the same regex inside a template expression no longer runs past its closing }. A regex literal after a keyword such as return, as in return />'/.test(s), is now recognized too.
#12021 59cc595 Thanks @dyc3! - Type inference performance has been significantly improved. Some popular libraries like Zod, Valibot, Arktype, Effect, Kysely, and Drizzle have gained a ~2-240x speedup in our benchmarks. This improvement affects all rules that use type information.
#12044 c73fb91 Thanks @dyc3! - Fixed #12042: the HTML formatter no longer removes the space between text and an inline element on the next line when it joins the lines.
- <p>a <em>b</em> c<u>d</u></p>
+ <p>a <em>b</em> c <u>d</u></p>#11965 f90bf38 Thanks @ematipico! - Fixed module resolution in long-running workspaces so imports reflect package manifest and TypeScript path-mapping changes without requiring the importing file to be edited.
#11860 0884e29 Thanks @dyc3! - Removed the attributes and functions options from the nursery rule noTailwindArbitraryValue. The rule now uses the same Tailwind detection as useTailwindShorthandClasses.
#11969 865cd30 Thanks @AlbinoGeek! - Fixed #11962: noUnknownTypeSelector no longer reports view transition names inside view transition pseudo-elements, such as page in ::view-transition-group(page).
#11914 06ff47b Thanks @dyc3! - Fixed #11897: the safe fix for noUselessStringConcat now escapes embedded double quotes when combining literals, preserving valid JavaScript and existing escape sequences.
#11997 af7825f Thanks @github-actions! - The noRestrictedDependencies rule has been updated with new module replacement data, it should now detect for more relevant replacements.
#11827 31bb662 Thanks @dfedoryshchev! - Fixed #11566: useNamingConvention no longer reports a namespace declared inside declare global or inside an external module declaration. Both positions are documented as always ignored, and the rule offered a safe fix, so biome check --write renamed the declaration:
export {}
declare global {
// no longer renamed to `Jsx`
namespace JSX {}
}#11814 23ba25f Thanks @siketyan! - Fixed type inference through generic type aliases that instantiate another generic type with a nested generic argument, such as type Nested<T> = Box<Wrapper<T>>. Type-aware rules now resolve members of such types:
declare const nested: Nested<number>;
// noUnnecessaryConditions now reports that `??` is unnecessary.
const inner = nested.value.inner ?? 1;#11908 dd5a5ce Thanks @siketyan! - Fixed #11880: Biome no longer misparses a << expression followed by a later >>> as TypeScript type arguments. For example, const mask = 1 << bits followed by const m = mask >>> 0 on the next line now parses correctly.
#11882 28c817d Thanks @mikehasa! - Fixed a bug in noOctalEscape where the safe fix could silently change a string's value. A legacy octal escape is at most two digits when the leading digit is 4-7, so "\751" is "\75" + "1" (i.e. "=1") but was rewritten to the single character ǩ; it is now rewritten to "\x3d1".
#11861 81b0adb Thanks @Netail! - Added the new nursery rule noSelfImport, which forbids a module from importing itself.
// foo.js
import foo from "./foo.js";#12041 5e14509 Thanks @ematipico! - Fixed a stack overflow in type-aware lint rules, such as noMisusedPromises and noFloatingPromises, when generic types in files that import each other reference one another in their type parameters.
// entity.ts
import type { Repository } from "./repository";
export interface Entity<R extends Repository<any> = Repository<any>> {}
// repository.ts
import type { Entity } from "./entity";
export interface Repository<E extends Entity<any> = Entity<any>> {}#11838 9bbff0c Thanks @dyc3! - Added the nursery rule usePromiseRejectErrors, which requires Error objects as Promise rejection reasons.
Promise.reject("Request failed");
new Promise((resolve, reject) => reject(42));#11917 717db8c Thanks @dyc3! - Added the nursery rule noMisplacedListElements for HTML and JSX, which requires <li> elements with an HTML element parent to be children of <ul>, <ol>, or <menu>. For example, <div><li>Item</li></div> is invalid.
#11919 8d0b990 Thanks @dyc3! - Fixed #11899: disabling a domain no longer disables rules that also belong to another enabled domain. For example, with "domains": { "react": "all", "next": "none" }, useExhaustiveDependencies and useHookAtTopLevel are now enabled.
Rules enabled explicitly in the configuration also stay enabled when one of their domains is set to "none".
#11814 23ba25f Thanks @siketyan! - Fixed #11810 and #11813: type-aware rules such as noUnnecessaryConditions and noFloatingPromises no longer take several seconds when a member is accessed on a recursive generic type alias, such as react-hook-form's FieldPathValue or zustand's Mutate.
#11983 cc39794 Thanks @AlbinoGeek! - Fixed #11939: the fix of useRegexLiterals no longer escapes a slash that is already escaped. new RegExp("\\/") is now fixed to /\// instead of the invalid /\\//.
#11869 3a21c80 Thanks @ematipico! - Fixed #9105: vcs.useIgnoreFile now evaluates parent directory patterns when matching child paths, preserving re-included directories such as !/src while ignoring their excluded siblings.
#11875 2cdd220 Thanks @dyc3! - Fixed #11867: noUndeclaredVariables incorrectly reported Vue slot props declared with v-slot or its # shorthand, including destructured props.
#12021 59cc595 Thanks @dyc3! - Type inference accuracy has been improved significantly. More global types, like Array, Map, Set, etc., are now fully defined. This should decrease false positives on all typed rules, since less types will be unknown.
#11929 aef690d Thanks @Th3S4mur41! - Fixed noUnknownProperty to recognize the frame-sizing CSS property.
#12022 6233eb2 Thanks @dyc3! - Fixed #12020: the HTML parser now reports an error for a mismatched closing tag like the </span> in <p>two</span></p>. Previously, it accepted </span> as the end of <p> because span contains the letter p, and the formatter deleted everything after it. HTML tag names are matched case-insensitively, so <DIV></div> is no longer reported as mismatched.
A closing tag with no opening tag at the top level of a file, like the second </p> in <p>a</p></p><p>b</p>, is now also reported as an error, instead of the formatter deleting it and everything after it.
#12037 48cdbb8 Thanks @ff1451! - Fixed #11898: noUselessReturn no longer offers a safe fix for a return; that is the body of an unbraced if, else, or label, because removing it produced invalid code. The safe fix now also keeps comments placed before or after the removed return;.
function foo() {
// Still reported, but the return is no longer removed
if (aborted) return;
}#12030 4ff83dd Thanks @ematipico! - Fixed #9155: Biome no longer reports a parse error for typed slot props in Vue files, such as v-slot="{ value }: { value: ValueType }". Types used in slot props annotations are now correctly detected as used by noUnusedVariables.
#11955 088164f Thanks @dyc3! - Fixed #11946: noUnreachable and useGetterReturn now recognize while and do...while loops with truthy literal conditions as infinite unless control flow exits the loop.
#11958 6964bfc Thanks @erenbati! - Fixed #11924: noFocusedTests no longer reports chained method calls such as builder.image(url).fit("max") as focused tests.
#11908 dd5a5ce Thanks @siketyan! - Fixed parsing of left shifts between TypeScript instantiation expressions. Biome now parses f<T> << f<T> as a left shift of two instantiation expressions, matching TypeScript, instead of reporting a parse error.
#11877 5a53b2c Thanks @dyc3! - Fixed #11278: noUnnecessaryConditions no longer incorrectly reports optional chaining on RegExp.exec() results, including patterns created with new RegExp(). Biome now infers the nullable RegExpExecArray | null return type, preserving necessary checks such as new RegExp(pattern).exec(input)?.[1].
#11906 b87822d Thanks @dyc3! - Fixed #11900: useForOf no longer reports loops that update their index inside the body, including i += 1 and argv[++i].
#11834 f89dd4f Thanks @dyc3! - Fixed incorrect type inference when generic parameters are reused across inherited types or swapped in recursive types.
Note truncated.
One column per quarter.