Version History
2.2.2 Latest
Patch Changes
-
#7266
b270bb5
Thanks @ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted. -
#7281
6436180
Thanks @ematipico! - Fixed an issue where the functionscanProject
wouldn’t work as expected. -
#7285
1511d0c
Thanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes. -
#7249
dff85c0
Thanks @ematipico! - Fixed #748, where Biome Language Server didn’t show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes. -
#7266
b270bb5
Thanks @ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely. -
#7209
679b70e
Thanks @patrickshipe! - Resolved an overcorrection inuseImportExtensions
when importing explicit index files.Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.
Example
// Beforeimport "./sub/index";import "./sub/index/index.js";// Afterimport "./sub/index";import "./sub/index.js"; -
#7270
953f9c6
Thanks @arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions. -
#7234
b7aa111
Thanks @JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.
-
#7283
0b07f45
Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using--config-path
. -
#7239
1d643d8
Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside.svelte.test.ts/js
and.svelte.spec.ts/js
files. -
#7264
62fdbc8
Thanks @ematipico! - Fixed a regression where when using--log-kind-pretty
wasn’t working anymore as expected. -
#7244
660031b
Thanks @JeetuSuthar! - Fixed #7225: ThenoExtraBooleanCast
rule now preserves parentheses when removingBoolean
calls inside negations.// Before!Boolean(b0 && b1);// After!(b0 && b1); // instead of !b0 && b1 -
#7298
46a8e93
Thanks @unvalley! - Fixed #6695:useNamingConvention
now correctly reports TypeScript parameter properties with modifiers.Previously, constructor parameter properties with modifiers like
private
orreadonly
were not checked against naming conventions. These properties are now treated consistently with regular class properties.
2.2.0
Minor Changes
-
#5506
1f8755b
Thanks @sakai-ast! - ThenoRestrictedImports
rule has been enhanced with a newpatterns
option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under
import-foo/
except forimport-foo/baz
.{"options": {"patterns": [{"group": ["import-foo/*", "!import-foo/baz"],"message": "import-foo is deprecated, except for modules in import-foo/baz."}]}}Invalid examples
import foo from "import-foo/foo";import bar from "import-foo/bar";Valid examples
import baz from "import-foo/baz";Additionally, the
patterns
option introducesimportNamePattern
to restrict specific import names using regular expressions. The following example restricts the import names that matchx
,y
orz
letters from modules underimport-foo/
.{"options": {"patterns": [{"group": ["import-foo/*"],"importNamePattern": "[xyz]"}]}}Invalid examples
import { x } from "import-foo/foo";Valid examples
import { foo } from "import-foo/foo";Furthermore, you can use the
invertImportNamePattern
boolean option to reverse this logic. When set to true, only the import names that match theimportNamePattern
will be allowed. The following configuration only allows the import names that matchx
,y
orz
letters from modules underimport-foo/
.{"options": {"patterns": [{"group": ["import-foo/*"],"importNamePattern": "[xyz]","invertImportNamePattern": true}]}}Invalid examples
import { foo } from "import-foo/foo";Valid examples
import { x } from "import-foo/foo"; -
#6506
90c5d6b
Thanks @nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:assist/source/useSortedKeys
now has asortOrder
optionassist/source/useSortedAttributes
now has asortOrder
optionassist/source/organizeImports
now has anidentifierOrder
option
For each of these options, the supported values are the same:
natural
. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g.A < a < B < b
) and number are compared in a human way (e.g.9
<10
). This is the default value.lexicographic
. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.
-
#7159
df3afdf
Thanks @ematipico! - Added the new ruleuseBiomeIgnoreFolder
. Since v2.2, Biome correctly prevents the indexing and crawling of folders.However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:
biome.json {"files": {"includes": ["!dist/**","!**/fixtures/**","!dist","!**/fixtures",]}} -
#6989
85b1128
Thanks @arendjr! - Fixed minor inconsistencies in howfiles.includes
was being handled.Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn’t specify the
/**
at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.This is no longer an issue and we now recommend to ignore folders without using the
/**
suffix. -
#7118
a78e878
Thanks @avshalomt2! - Added support for.graphqls
files. Biome can now format and lint GraphQL files that have the extension.graphqls
-
#6159
f02a296
Thanks @bavalpey! - Added a new option to Biome’s JavaScript formatter,javascript.formatter.operatorLinebreak
, to configure whether long lines should be broken before or after binary operators.For example, the following configuration:
{formatter: {javascript: {operatorLinebreak: "before", // defaults to "after"},},}Will cause this JavaScript file:
const VERY_LONG_CONDITION_1234123412341234123412341234 = false;if (VERY_LONG_CONDITION_1234123412341234123412341234 &&VERY_LONG_CONDITION_1234123412341234123412341234 &&VERY_LONG_CONDITION_1234123412341234123412341234 &&VERY_LONG_CONDITION_1234123412341234123412341234) {console.log("DONE");}to be formatted like this:
const VERY_LONG_CONDITION_1234123412341234123412341234 = false;if (VERY_LONG_CONDITION_1234123412341234123412341234 &&VERY_LONG_CONDITION_1234123412341234123412341234 &&VERY_LONG_CONDITION_1234123412341234123412341234 &&VERY_LONG_CONDITION_1234123412341234123412341234) {console.log("DONE");} -
#7137
a653a0f
Thanks @ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.Promoted rules
The following rules have been promoted from nursery to stable groups:
CSS
- Promoted
noImportantStyles
to thecomplexity
group. - Promoted
noUnknownAtRules
to thesuspicious
group.
GraphQL
- Promoted
useGraphqlNamedOperations
to thecorrectness
group. - Promoted
useGraphqlNamingConvention
to thestyle
group.
JavaScript/TypeScript
- Promoted
noExcessiveLinesPerFunction
to thecomplexity
group. - Promoted
noImplicitCoercions
to thecomplexity
group. - Promoted
useIndexOf
to thecomplexity
group. - Promoted
noGlobalDirnameFilename
to thecorrectness
group. - Promoted
noNestedComponentDefinitions
to thecorrectness
group. - Promoted
noProcessGlobal
to thecorrectness
group. - Promoted
noReactPropAssignments
to thecorrectness
group. - Promoted
noRestrictedElements
to thecorrectness
group. - Promoted
noSolidDestructuredProps
to thecorrectness
group. - Promoted
useJsonImportAttributes
to thecorrectness
group. - Promoted
useParseIntRadix
to thecorrectness
group. - Promoted
useSingleJsDocAsterisk
to thecorrectness
group. - Promoted
useUniqueElementIds
to thecorrectness
group. - Promoted
noAwaitInLoops
to theperformance
group. - Promoted
noUnwantedPolyfillio
to theperformance
group. - Promoted
useGoogleFontPreconnect
to theperformance
group. - Promoted
useSolidForComponent
to theperformance
group. - Promoted
noMagicNumbers
to thestyle
group. - Promoted
useConsistentObjectDefinitions
to thestyle
group. - Promoted
useExportsLast
to thestyle
group. - Promoted
useGroupedAccessorPairs
to thestyle
group. - Promoted
useNumericSeparators
to thestyle
group. - Promoted
useObjectSpread
to thestyle
group. - Promoted
useReadonlyClassProperties
to thestyle
group. - Promoted
useSymbolDescription
to thestyle
group. - Promoted
useUnifiedTypeSignatures
to thestyle
group. - Promoted
noBitwiseOperators
to thesuspicious
group. - Promoted
noConstantBinaryExpressions
to thesuspicious
group. - Promoted
noTsIgnore
to thesuspicious
group. - Promoted
noUnassignedVariables
to thesuspicious
group. - Promoted
noUselessRegexBackrefs
to thesuspicious
group. - Promoted
noUselessEscapeInString
to thesuspicious
group. - Promoted
useIterableCallbackReturn
to thesuspicious
group. - Promoted
useStaticResponseMethods
to thesuspicious
group.
Renamed rules
The following rules have been renamed during promotion. The migration tool will automatically update your configuration:
- Renamed
noAwaitInLoop
tonoAwaitInLoops
. - Renamed
noConstantBinaryExpression
tonoConstantBinaryExpressions
. - Renamed
noDestructuredProps
tonoSolidDestructuredProps
. - Renamed
noImplicitCoercion
tonoImplicitCoercions
. - Renamed
noReactPropAssign
tonoReactPropAssignments
. - Renamed
noUnknownAtRule
tonoUnknownAtRules
. - Renamed
noUselessBackrefInRegex
tonoUselessRegexBackrefs
. - Renamed
useAdjacentGetterSetter
touseGroupedAccessorPairs
. - Renamed
useConsistentObjectDefinition
touseConsistentObjectDefinitions
. - Renamed
useConsistentResponse
touseStaticResponseMethods
. - Renamed
useForComponent
touseSolidForComponent
. - Renamed
useJsonImportAttribute
touseJsonImportAttributes
. - Renamed
useNamedOperation
touseGraphqlNamedOperations
. - Renamed
useNamingConvention
touseGraphqlNamingConvention
. - Renamed
useUnifiedTypeSignature
touseUnifiedTypeSignatures
.
Configuration files using the old rule names will need to be updated. Use the migration tool to automatically update your configuration:
Terminal window biome migrate --write - Promoted
-
#7159
df3afdf
Thanks @ematipico! - Added the new rulenoBiomeFirstException
. This rule prevents the incorrect usage of patterns insidefiles.includes
.This rule catches if the first element of the array contains
!
. This mistake will cause Biome to analyze no files:biome.json {files: {includes: ["!dist/**"], // this is an error},} -
#6923
0589f08
Thanks @ptkagori! - Added Qwik Domain to BiomeThis release introduces Qwik domain support in Biome, enabling Qwik developers to use Biome as a linter and formatter for their projects.
- Added the Qwik domain infrastructure to Biome.
- Enabled the following rules for Qwik:
-
#6989
85b1128
Thanks @arendjr! - Fixed #6965: Implemented smarter scanner for project rules.Previously, if project rules were enabled, Biome’s scanner would scan all dependencies regardless of whether they were used by/reachable from source files or not. While this worked for a first version, it was far from optimal.
The new scanner first scans everything listed under the
files.includes
setting, and then descends into the dependencies that were discovered there, including transitive dependencies. This has three main advantages:- Dependencies that are not reachable from your source files don’t get indexed.
- Dependencies that have multiple type definitions, such as those with separate definitions for CommonJS and ESM imports, only have the relevant definitions indexed.
- If
vcs.useIgnoreFile
is enabled,.gitignore
gets respected as well. Assuming you have folders such asbuild/
ordist/
configured there, those will be automatically ignored by the scanner.
The change in the scanner also has a more nuanced impact: Previously, if you used
files.includes
to ignore a file in an included folder, the scanner would still index this file. Now the file is fully ignored, unless you import it.As a user you should notice better scanner performance (if you have project rules enabled), and hopefully you need to worry less about configuring
files.experimentalScannerIgnores
. Eventually our goal is still to deprecate that setting, so if you’re using it today, we encourage you to see which ignores are still necessary there, and whether you can achieve the same effect by ignoring paths usingfiles.includes
instead.None of these changes affect the scanner if no project rules are enabled.
-
#6731
d6a05b5
Thanks @ematipico! - The--reporter=summary
has been greatly enhanced. It now shows the list of files that contains violations, the files shown are clickable and can be opened from the editor.Below an example of the new version:
reporter/parse ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━i The following files have parsing errors.- index.cssreporter/format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━i The following files needs to be formatted.- index.css- index.ts- main.tsreporter/violations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━i Some lint rules or assist actions reported some violations.Rule Name Diagnosticslint/correctness/noUnknownFunction 14 (2 error(s), 12 warning(s), 0 info(s))lint/suspicious/noImplicitAnyLet 16 (12 error(s), 4 warning(s), 0 info(s))lint/suspicious/noDoubleEquals 8 (8 error(s), 0 warning(s), 0 info(s))assist/source/organizeImports 2 (2 error(s), 0 warning(s), 0 info(s))lint/suspicious/noRedeclare 12 (12 error(s), 0 warning(s), 0 info(s))lint/suspicious/noDebugger 8 (8 error(s), 0 warning(s), 0 info(s)) -
#6896
527db7f
Thanks @ematipico! - Added new functions to the@biomejs/wasm-*
packages:fileExists
: returns whether the input file exists in the workspace.isPathIgnored
: returns whether the input path is ignored.updateModuleGraph
: updates the internal module graph of the input path.getModuleGraph
: it returns a serialized version of the internal module graph.scanProject
: scans the files and directories in the project to build the internal module graph.
-
#6398
d1a315d
Thanks @josh-! - Added support for tracking stable results in user-provided React hooks that return objects touseExhaustiveDependencies
to compliment existing support for array return values. For example:biome.json {// rule optionsuseExhaustiveDependencies: {level: "error",options: {hooks: [{name: "useCustomHook",stableResult: ["setMyState"],},],},},}This will allow the following to be validated:
const { myState, setMyState } = useCustomHook();const toggleMyState = useCallback(() => {setMyState(!myState);}, [myState]); // Only `myState` needs to be specified here. -
#7201
2afaa49
Thanks @Conaclos! - Implemented #7174.useConst
no longer reports variables that are read before being written.Previously,
useConst
reported uninitialised variables that were read in an inner function before being written, as shown in the following example:let v;function f() {return v;}v = 0;This can produce false positives in the case where
f
is called beforev
has been written, as in the following code:let v;function f() {return v;}console.log(f()); // print `undefined`v = 0;Although this is an expected behavior of the original implementation, we consider it problematic since the rule’s fix is marked as safe. To avoid false positives like this, the rule now ignores the previous examples. However, this has the disadvantage of resulting in false negatives, such as not reporting the first example.
Patch Changes
-
#7156
137d111
Thanks @ematipico! - Fixed #7152. Now the rulenoDuplicateFontNames
correctly detects font names with spaces e.g.Liberation Mono
. The diagnostic of the rule now points to the first instances of the repeated font.The following example doesn’t trigger the rule anymore:
c {font-family:SF Mono,Liberation Mono,sans-serif;}d {font:1em SF Mono,Liberation Mono,sans-serif;} -
#6907
7331bb9
Thanks @ematipico! - Added a new experimental option that allows parsing of.html
files that contain interpolation syntax.biome.json {html: {// This is the new, experimental option.parser: {interpolation: true,},},}<h1>{{ $title }}</h1> -
#7124
3f436b8
Thanks @Jayllyz! - Added the ruleuseMaxParams
.This rule enforces a maximum number of parameters for functions to improve code readability and maintainability. Functions with many parameters are difficult to read, understand, and maintain because they require memorizing parameter order and types.
// Invalid - too many parameters (default max: 4)function processData(name,age,email,phone,address,city,country,zipCode,) {// ...}// Valid - within parameter limitfunction processData(userData) {const { name, age, email, phone, address, city, country, zipCode } =userData;// ...}function calculateSum(a, b, c) {return a + b + c;} -
#7161
1a14a59
Thanks @ematipico! - Fixed #7160. Now Biome correctly computes ignored files when usingformatter.includes
,linter.includes
andassist.includes
inside nested configurations that use"extends": "//"
. -
#7081
a081bbe
Thanks @Jayllyz! - Added the rulenoNextAsyncClientComponent
.This rule prevents the use of async functions for client components in Next.js applications. Client components marked with “use client” directive should not be async as this can cause hydration mismatches, break component rendering lifecycle, and lead to unexpected behavior with React’s concurrent features.
"use client";// Invalid - async client componentexport default async function MyComponent() {return <div>Hello</div>;}// Valid - synchronous client componentexport default function MyComponent() {return <div>Hello</div>;} -
#7171
5241690
Thanks @siketyan! - Fixed #7162: ThenoUndeclaredDependencies
rule now considers a type-only import as a dev dependency.For example, the following code is no longer reported:
package.json
:{"devDependencies": {"type-fest": "*"}}foo.ts
:import type { SetRequired } from "type-fest";Note that you still need to declare the package in the
devDependencies
section inpackage.json
.
2.1.4
Patch Changes
-
#7121
b9642ab
Thanks @arendjr! - Fixed #7111: Imported symbols using aliases are now correctly recognised. -
#7103
80515ec
Thanks @omasakun! - Fixed #6933 and #6994.When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.
-
#6887
0cc38f5
Thanks @ptkagori! - Added thenoQwikUseVisibleTask
rule to Qwik.This rule is intended for use in Qwik applications to warn about the use of
useVisibleTask$()
functions which require careful consideration before use.Invalid:
useVisibleTask$(() => {console.log("Component is visible");});Valid:
useTask$(() => {console.log("Task executed");}); -
#7084
50ca155
Thanks @ematipico! - Added the new nursery rulenoUnnecessararyConditions
, which detects whenever some conditions don’t change during the life cycle of the program, and truthy or false, hence deemed redundant.For example, the following snippets will trigger the rule:
// Always truthy literal conditionsif (true) {console.log("always runs");}// Unnecessary condition on constrained string typefunction foo(arg: "bar" | "baz") {if (arg) {// This check is unnecessary}} -
#6887
0cc38f5
Thanks @ptkagori! - Added theuseImageSize
rule to Biome.The
useImageSize
rule enforces the use of width and height attributes on<img>
elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.Invalid:
<img src="/image.png" /><img src="https://example.com/image.png" /><img src="/image.png" width="200" /><img src="/image.png" height="200" />Valid:
<img width="200" height="600" src="/static/images/portrait-01.webp" /><img width="100" height="100" src="https://example.com/image.png" /> -
#6887
0cc38f5
Thanks @ptkagori! - Added theuseAnchorHref
rule to Biome.The
useAnchorHref
rule enforces the presence of anhref
attribute on<a>
elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.Invalid:
<a>Link</a><a target="_blank">External</a>Valid:
<a href="/home">Home</a><a href="https://example.com" target="_blank">External</a> -
#7100
29fcb05
Thanks @Jayllyz! - Added the rulenoNonNullAssertedOptionalChain
.This rule prevents the use of non-null assertions (
!
) immediately after optional chaining expressions (?.
). Optional chaining is designed to safely handle nullable values by returningundefined
when the chain encountersnull
orundefined
. Using a non-null assertion defeats this purpose and can lead to runtime errors.// Invalid - non-null assertion after optional chainingobj?.prop!;obj?.method()!;obj?.[key]!;obj?.prop!;// Valid - proper optional chaining usageobj?.prop;obj?.method();obj?.prop ?? defaultValue;obj!.prop?.method(); -
#7129
9f4538a
Thanks @drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions -
#7106
236deaa
Thanks @arendjr! - Fixed #6985: Inference of return types no longer mistakenly picks up return types of nested functions. -
#7102
d3118c6
Thanks @omasakun! - Fixed #7101:noUnusedPrivateClassMembers
now handles members declared as part of constructor arguments:- If a class member defined in a constructor argument is only used within the constructor, it removes the
private
modifier and makes it a plain method argument. - If it is not used at all, it will prefix it with an underscore, similar to
noUnusedFunctionParameter
.
- If a class member defined in a constructor argument is only used within the constructor, it removes the
-
#7104
5395297
Thanks @harxki! - Reverting to prevent regressions around ref handling -
#7143
1a6933a
Thanks @siketyan! - Fixed #6799: ThenoImportCycles
rule now ignores type-only imports if the newignoreTypes
option is enabled (enabled by default).[!WARNING] Breaking Change: The
noImportCycles
rule no longer detects import cycles that include one or more type-only imports by default. To keep the old behaviour, you can turn off theignoreTypes
option explicitly:{"linter": {"rules": {"nursery": {"noImportCycles": {"options": {"ignoreTypes": false}}}}}} -
#7099
6cc84cb
Thanks @arendjr! - Fixed #7062: Biome now correctly considers extended configs when determining the mode for the scanner. -
#6887
0cc38f5
Thanks @ptkagori! - Added theuseQwikClasslist
rule to Biome.This rule is intended for use in Qwik applications to encourage the use of the built-in
class
prop (which accepts a string, object, or array) instead of theclassnames
utility library.Invalid:
<div class={classnames({ active: true, disabled: false })} />Valid:
<div classlist={{ active: true, disabled: false }} /> -
#7019
57c15e6
Thanks @fireairforce! - Added support in the JS parser forimport source
(a stage3 proposal). The syntax looks like:import source foo from "<specifier>"; -
#7053
655049e
Thanks @jakeleventhal! - Added theuseConsistentTypeDefinitions
rule.This rule enforces consistent usage of either
interface
ortype
for object type definitions in TypeScript.The rule accepts an option to specify the preferred style:
interface
(default): Prefer usinginterface
for object type definitionstype
: Prefer usingtype
for object type definitions
Examples:
// With default option (interface)// ❌ Invalidtype Point = { x: number; y: number };// ✅ Validinterface Point {x: number;y: number;}// With option { style: "type" }// ❌ Invalidinterface Point {x: number;y: number;}// ✅ Validtype Point = { x: number; y: number };The rule will automatically fix simple cases where conversion is straightforward.
2.1.3
Patch Changes
-
#7057
634a667
Thanks @mdevils! - Added the rulenoVueReservedKeys
, which prevents the use of reserved Vue keys.It prevents the use of Vue reserved keys such as those starting with like
$el
,$data
,$props
) and keys starting with\_
in data properties, which can cause conflicts and unexpected behavior in Vue components.Invalid example
<script>export default {data: {$el: "",_foo: "bar",},};</script><script>export default {computed: {$data() {return this.someData;},},};</script>Valid examples
<script>export default {data() {return {message: "Hello Vue!",count: 0,};},};</script><script>export default {computed: {displayMessage() {return this.message;},},};</script> -
#6941
734d708
Thanks @JamBalaya56562! - Added@eslint-react/no-nested-component-definitions
as a rule source fornoNestedComponentDefinitions
. Now it will get picked up bybiome migrate --eslint
. -
#6463
0a16d54
Thanks @JamBalaya56562! - Fixed a website link for theuseComponentExportOnlyModules
linter rule to point to the correct URL. -
#6944
e53f2fe
Thanks @sterliakov! - Fixed #6910: Biome now ignores type casts and assertions when evaluating numbers fornoMagicNumbers
rule. -
#6991
476cd55
Thanks @denbezrukov! - Fixed #6973: Add support for parsing the :active-view-transition-type() pseudo-class:active-view-transition-type(first second) {} -
#6992
0b1e194
Thanks @ematipico! - Added a new JSON rule callednoQuickfixBiome
, which disallow the use of code actionquickfix.biome
inside code editor settings. -
#6943
249306d
Thanks @JamBalaya56562! - Fixed@vitest/eslint-plugin
source url. -
#6947
4c7ed0f
Thanks @JamBalaya56562! - Fixed ESLint migration for the ruleprefer-for
fromeslint-plugin-solid
to Biome’suseForComponent
. -
#6976
72ebadc
Thanks @siketyan! - Fixed #6692: The rulesnoUnusedVariables
andnoUnusedFunctionParameters
no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope). -
#6990
333f5d0
Thanks @rvanlaarhoven! - Fixed the documentation URL forlint/correctness/noUnknownPseudoClass
-
#7000
4021165
Thanks @harxki! - Fixed #6795:noUnassignedVariables
now correctly recognizes variables used in JSXref
attributes. -
#7044
b091ddf
Thanks @ematipico! - Fixed #6622, now the ruleuseSemanticElements
works for JSX self-closing elements too. -
#7014
c4864e8
Thanks @siketyan! - Fixed #6516: Thebiome migrate
command no longer break the member list with trailing comments. -
#6979
29cb6da
Thanks @unvalley! - Fixed #6767:useSortedClasses
now correctly removes leading and trailing whitespace in className.Previously, trailing spaces in className were not fully removed.
// Think we have this code:<div className="text-sm font-bold " />// Before: applied fix, but a trailing space was preserved<div className="font-bold text-sm " />// After: applied fix, trailing spaces removed<div className="font-bold text-sm" /> -
#7055
ee4828d
Thanks @dyc3! - Added the nursery ruleuseReactFunctionComponents
. This rule enforces the preference to use function components instead of class components.Valid:
function Foo() {return <div>Hello, world!</div>;}Invalid:
class Foo extends React.Component {render() {return <div>Hello, world!</div>;}} -
#6924
2d21be9
Thanks @ematipico! - Fixed #113, where the Biome Language Server didn’t correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved. -
#6931
e6b2380
Thanks @arendjr! - Fixed #6915:useHookAtTopLevel
no longer hangs when rules call themselves recursively. -
#7012
01c0ab4
Thanks @siketyan! - Fixed #5837: Invalid suppression comments such asbiome-ignore-all-start
orbiome-ignore-all-end
no longer causes a panic. -
#6949
48462f8
Thanks @fireairforce! - Support parseimport defer
(which is a stage3 proposal). The syntax look like this:import defer * as foo from "<specifier>"; -
#6938
5feb5a6
Thanks @vladimir-ivanov! - Fixed #6919 and #6920:useReadonlyClassProperties
now does checks for mutations in async class methods.Example:
class Counter3 {private counter: number;async count() {this.counter = 1;const counterString = `${this.counter++}`;}} -
#6942
cfda528
Thanks @sterliakov! - Fixed #6939. Biome now understandsthis
binding in classes outside of methods.
2.1.2
Patch Changes
-
#6865
b35bf64
Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)div {box-sizing: border-box;color: red;} -
#6798
3579ffa
Thanks @dyc3! - Fixed #6762, Biome now knows that~/.config/zed/settings.json
and~/.config/Code/User/settings.json
allows comments by default. -
#6839
4cd62d8
Thanks @ematipico! - Fixed #6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files). -
#6879
0059cd9
Thanks @denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon Previously, accessing a declaration from a list required an extra step:item.as_any_css_declaration_with_semicolon().as_css_declaration_with_semicolon()Now, it can be done directly with:
item.as_css_declaration_with_semicolon() -
#6839
4cd62d8
Thanks @ematipico! - Fixed a bug where the Biome Language Server didn’t correctly ignore specific files whenvcs.useIgnoreFile
is set totrue
. -
#6884
5ff50f8
Thanks @arendjr! - Improved the performance ofnoImportCycles
by ~30%. -
#6903
241dd9e
Thanks @arendjr! - Fixed #6829: Fixed a false positive reported byuseImportExtensions
when importing a.js
file that had a matching.d.ts
file in the same folder. -
#6846
446112e
Thanks @darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix. -
#6823
eebc48e
Thanks @arendjr! - Improved #6172: Optimised the way function arguments are stored in Biome’s type inference. This led to about 10% performance improvement inRedisCommander.d.ts
and about 2% on@next/font
type definitions. -
#6878
3402976
Thanks @ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code actionquickfix.biome
.Now Biome no longer applies an unsafe code fix when using the code action
quickfix.biome
. -
#6794
4d5fc0e
Thanks @vladimir-ivanov! - Fixed #6719: ThenoInvalidUseBeforeDeclaration
rule covers additional use cases.Examples:
type Bar = { [BAR]: true };const BAR = "bar";interface Bar {child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };}const BAR = "bar";enum EnumFoo {BAR = "bar",} -
#6863
531e97e
Thanks @dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #6815. -
#6832
bdbc2b1
Thanks @togami2864! - Fixed #6165: Fixed false negative innoUnusedPrivateClassMembers
rule when checking member usage in classes -
#6839
4cd62d8
Thanks @ematipico! - Fixed a bug where the root ignore file wasn’t correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.Now, when using
vcs.useIgnoreFile
, the the globs specified in the ignore file from the project root will have the same semantics as thefiles.includes
setting of the root configuration.Refer to the relative web page to understand how they work.
-
#6898
5beb024
Thanks @arendjr! - Fixed #6891: Improved type inference for array indices.Example:
const numbers: number[];numbers[42]; // This now infers to `number | undefined`. -
#6809
8192451
Thanks @arendjr! - Fixed #6796: Fixed a false positive that happened innoFloatingPromises
when calling functions that were declared as part offor ... of
syntax insideasync
functions.Instead, the variables declared inside
for ... of
loops are now correctly inferred if the expression being iterated evaluates to anArray
(support for other iterables will follow later).Invalid example
const txStatements: Array<(tx) => Promise<any>> = [];db.transaction((tx: any) => {for (const stmt of txStatements) {// We correctly flag this resolves to a `Promise`:stmt(tx);}});Valid example
async function valid(db) {const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];db.transaction((tx: any) => {for (const stmt of txStatements) {// We don't flag a false positive here anymore:stmt(tx);}});} -
#6757
13a0818
Thanks @mdevils! - Added the rulenoVueReservedProps
, resolves #6309.It prevents the use of reserved Vue prop names such as
key
andref
which can cause conflicts and unexpected behavior in Vue components.Invalid example
import { defineComponent } from "vue";export default defineComponent({props: ["ref", "key", "foo"],});<script setup>defineProps({ref: String,key: String,foo: String,});</script>Valid examples
import { defineComponent } from "vue";export default defineComponent({props: ["foo"],});<script setup>defineProps({ foo: String });</script> -
#6840
1a57b51
Thanks @denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.::part(first second) {} -
#6845
4fd44ec
Thanks @arendjr! - Fixed #6510: The scanner no longer shows diagnostics on inaccessible files unless--verbose
is used. -
#6844
b7e2d4d
Thanks @sterliakov! - Fixed #6837: Fixed regression with multiple consecutive line suppression comments using instances (like// biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason
). -
#6818
5f3f5a6
Thanks @siketyan! - Fixed an issue wheretextDocument/codeAction
in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file. -
#6804
3e6ab16
Thanks @arendjr! -noFloatingPromises
will no longer suggest to addawait
keyword inside synchronous callbacks nested insideasync
functions. -
#6901
c9e969a
Thanks @arendjr! - Fixed #6777: Fixed type inference handling ofthis
to avoid infinite recursion.Thanks to @sterliakov for the thorough investigation!
-
#6855
d1581c7
Thanks @vladimir-ivanov! - Fixed #6775:useReadonlyClassProperties
now also captures mutations inside function arguments.Example:
class Counter {private counter: number;count() {console.log(this.counter++);const counterString = `${this.counter++}`;}} -
#6839
4cd62d8
Thanks @ematipico! - Fixed a bug where Biome didn’t throw any error whenvcs.useIgnoreFile
is set totrue
, and there wasn’t any ignore file read. Now Biome correctly throws an error if no ignore files are found. -
#6911
6d68074
Thanks @arendjr! - Fixed #6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as
build/
ordist/
folders.With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.
Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.
2.1.1
Patch Changes
-
#6781
9bbd34f
Thanks @siketyan! - Fixed theFileFeaturesResult
interface in the WASM API was defined as a mapped object but the actual value was aMap
object. -
#6761
cf3c2ce
Thanks @dyc3! - Fixed #6759, a false positive fornoFocusedTests
that was triggered by calling any function with the namefit
on any object.The following code will now pass the
noFocusedTests
rule:import foo from "foo";foo.fit();
2.1.0
Minor Changes
-
#6512
0c0bf82
Thanks @arendjr! - The rulenoFloatingPromises
can now detect floating arrays ofPromise
s.Invalid examples
// This gets flagged because the Promises are not handled.[1, 2, 3].map(async (x) => x + 1);Valid examples
await Promise.all([1, 2, 3].map(async (x) => x + 1)); -
#6637
6918085
Thanks @arendjr! - Type inference is now able to handle the sequence operator (,
), as well as post- and pre-update operators:++
.Example
let x = 5;// We now infer that `x++` resolves to a number, while the expression as a whole// becomes a Promise:(x++, new Promise((resolve) => resolve("comma"))); -
#6752
c9eaca4
Thanks @arendjr! - Fixed #6646:.gitignore
files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored throughfiles.includes
. -
#6746
90aeead
Thanks @arendjr! -biome migrate
no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.Users who are upgrading from Biome 1.x are therefore advised to first upgrade to Biome 2.0, and run the migration, before continuing to Biome 2.1 or later.
-
#6583
d415a3f
Thanks @arendjr! - Added the nursery rulenoMisusedPromises
.It signals
Promise
s in places where conditionals or iterables are expected.Invalid examples
const promise = Promise.resolve("value");// Using a `Promise` as conditional is always truthy:if (promise) {/* ... */}// Spreading a `Promise` has no effect:console.log({ foo: 42, ...promise });// This does not `await` the `Promise`s from the callbacks,// so it does not behave as you may expect:[1, 2, 3].forEach(async (value) => {await fetch(`/${value}`);});Valid examples
const promise = Promise.resolve("value");if (await promise) {/* ... */}console.log({ foo: 42, ...(await promise) }); -
#6405
cd4a9bb
Thanks @vladimir-ivanov! - Added theignoreRestSiblings
option to thenoUnusedFunctionParameters
rule.This option is used to ignore unused function parameters that are siblings of the rest parameter.
The default is
false
, which means that unused function parameters that are siblings of the rest parameter will be reported.Example
{"rules": {"noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]}} -
#6614
0840021
Thanks @arendjr! - We have implemented a more targeted version of the scanner, which ensures that if you provide file paths to handle on the CLI, the scanner will exclude directories that are not relevant to those paths.Note that for many commands, such as
biome check
andbiome format
, the file paths to handle are implicitly set to the current working directory if you do not provide any path explicitly. The targeted scanner also works with such implicit paths, which means that if you run Biome from a subfolder, other folders that are part of the project are automatically exempted.Use cases where you invoke Biome from the root of the project without providing a path, as well as those where project rules are enabled, are not expected to see performance benefits from this.
-
#6488
c5ee385
Thanks @ianzone! -nx.json
andproject.json
have been added to the list of well-known files. -
#6720
52e36ae
Thanks @minht11! - Added$
symbol to organizeImports:ALIAS:
group.import { action } from '$lib'
will be treated as alias import.
Patch Changes
-
#6712
2649ac6
Thanks @sterliakov! - Fixed #6595: Biome now supports// biome-ignore-all
file-level suppressions in files that start with a shebang (#!
). -
#6758
28dc49e
Thanks @arendjr! - Fixed #6573: Grit plugins can now match bare imports.Example
The following snippet:
`import $source`will now match:
import "main.css"; -
#6550
b424f46
Thanks @arendjr! - Type inference is now able to handle logical expressions:&&
,||
, and??
.Examples
// We can now infer that because `true` is truthy, the entire expression// evaluates to a `Promise`.true && Promise.reject("logical operator bypass");// And we know that this doesn't:false && Promise.reject("logical operator bypass");// Truthiness, falsiness, and non-nullishness can all be determined on more// complex expressions as well. So the following also works:type Nullish = null | undefined;type Params = {booleanOption: boolean | Nullish;falsyOption: false | Nullish;};function foo({ booleanOption, falsyOption }: Params) {// This may be a Promise:booleanOption ?? Promise.reject("logical operator bypass");// But this never is:falsyOption && Promise.reject("logical operator bypass");} -
#6413
4aa0e50
Thanks @wojtekmaj! - Improved error message inuseDateNow
rule. -
#6673
341e062
Thanks @dyc3! - Fixed a case where the HTML formatter would mangle embedded language tags ifwhitespaceSensitivity
was set tostrict
-
#6642
a991229
Thanks @unvalley! - Fixed #4494: ThenoSecrets
rule now correctly uses theentropyThreshold
option to detect secret like strings. -
#6520
0c43545
Thanks @arendjr! - Type inference is now able to handle ternary conditions in type aliases.Note that we don’t attempt to evaluate the condition itself. The resulting type is simply a union of both conditional outcomes.
Example
type MaybeResult<T> = T extends Function ? Promise<string> : undefined;// We can now detect this function _might_ return a `Promise`:function doStuff<T>(input: T): MaybeResult<T> {/* ... */} -
#6711
1937691
Thanks @sterliakov! - Fixed #6654: Fixed range highlighting of<explanation>
placeholder in inline suppression block comments. -
#6756
d12b26f
Thanks @dyc3! - Fixed #6669: Added an exception tonoUnusedImports
to allow type augmentation imports.import type {} from "@mui/lab/themeAugmentation"; -
Fixed #4994: LSP server registered some capabilities even when the client did not support dynamic registration.
-
#6599
5e611fa
Thanks @vladimir-ivanov! - Fixed #6380: ThenoFocusedTests
rule now correctly displays the function name in the diagnostic message when a test is focused.Every instance of a focused test function (like
fdescribe
,fit
,ftest
andonly
) had the word ‘only’ hardcoded. This has been updated to use the actual function name, so the message is now more accurate and specific.Example for
fdescribe
:i The 'fdescribe' method is often used for debugging or during implementation.i Consider removing 'f' prefix from 'fdescribe' to ensure all tests are executed. -
#6671
0c9ab43
Thanks @vladimir-ivanov! - Fixed #6634: TheuseReadonlyClassProperties
rule now correctly flags mutations in class getters and in arrow functions within class properties.Examples:
class GetterWithMutationValue {#value: string;get value() {if (!this.#value) {this.#value = "defaultValue";}return this.#value;}}class ClassPropertyArrowFunctionWithMutation {private bar: string | null = null;readonly action = () => {this.bar = "init";};} -
#6682
ca04cea
Thanks @ematipico! - Fixed #6668: Biome Assist is now enabled by default for CSS files. -
#6525
66b089c
Thanks @arendjr! - Type inference can now infer the return types of functions and methods without annotations.Examples
const sneakyObject = {doSomething() {return Promise.resolve("This is a floating promise!");},};// We can now detect that `doSomething()` returns a `Promise`.sneakyObject.doSomething(); -
#6531
c06df79
Thanks @arendjr! - Biome’s type inference now detects the type of properties with getters.Examples
const sneakyObject2 = {get something() {return new Promise((_, reject) => reject("This is a floating promise!"));},};// We now detect this is a Promise:sneakyObject2.something; -
#6587
a330fcc
Thanks @Conaclos! -organizeImports
is now able to sort named specifiers and import attributes with bogus nodes. -
#6618
6174869
Thanks @Shinyaigeek! - Fixed #6610: JSON import attributes are now correctly detected when they contain extra whitespace. -
#6753
fce5d2c
Thanks @dyc3! - Improved the error messages when Biome is provided incompatible arguments on the CLI. -
#6587
a330fcc
Thanks @Conaclos! - Fixed #6491: The action ofuseSortedKeys
removed comments or wrongly transferred them to distinct nodes. -
#6696
92964a7
Thanks @unvalley! - Fixed #6633: ThenoImplicitCoercion
rule no longer reports diagnostics for1 / value
expressions.1 / value; // no error -
#6683
43d871e
Thanks @ematipico! - Fixed #6537: Biome no longer removes the trailing comma from JSON files whenformatter.json.trailingCommas
is explicitly set to"all"
. -
#6693
bfdce0b
Thanks @dyc3! - Fixed #6691: The HTML parser will now consider.
to be a valid character for tag names. -
#6716
ead03d1
Thanks @siketyan! - The Biome LSP server no longer responds with an error for atextDocument/codeActions
request when Biome doesn’t support a feature for the file (e.g. Code actions aren’t supported in GritQL files). -
#6679
7bf9a60
Thanks @marko-hologram! - Fixed #6638: JavaScript formatteroverrides
options now correctly overrideexpand
option. JSON formatteroverrides
options now correctly overridebracketSpacing
andexpand
options. -
#6717
7f5b541
Thanks @siketyan! - Fixed #6688: thenoUselessFragments
no longer reports<Fragment />
elements that includes HTML character entities. -
#6600
853e1b5
Thanks @daivinhtran! - Fixed #4677: ThenoUnusedImports
rule won’t produce diagnostics for types used in comments of static members anymore. -
#6662
3afc804
Thanks @arendjr! - If a nested configuration file is ignored by the root configuration, it will now actually be ignored.Biome has an exception in place for configuration files so they cannot be ignored, because the configuration files are vital to Biome itself. But this exception was incorrectly applied to nested configurations as well. Now only the root configuration is exempt from being ignored.
-
#6596
c0718ca
Thanks @ematipico! - Fixed #6566: Biome no longer errors when using the option--files-ignore-unknown=true
instdin
mode.Biome has also become less strict when using
--stdin-file-path
instdin
mode. It will no longer error if the file path doesn’t contain an extension, but instead it will return the original content. -
#6562
153eda7
Thanks @vladimir-ivanov! - Added the nursery rule noMagicNumbers. The rule detects and reports the use of “magic numbers” — numeric literals that are used directly in code without being assigned to a named constant.Example
let total = price * 1.23; // Magic number for tax rate will highlight 1.23 as magic number -
#6663
af78d6d
Thanks @ematipico! - Fixed #6656: Biome now correctly formats HTML void elements such as<meta>
when they contain a self-closing slash.<meta foo="bar" /><meta foo="bar"> -
#6732
31e4396
Thanks @vladimir-ivanov! - Resolved #6281: Improved performance of handlingpackage.json
files in the scanner. -
#6625
19cb475
Thanks @arendjr! - Fixed #6616: Fixed an issue with extending configurations that contained an explicitroot
field while the configuration in the project did not. -
#6650
19aab18
Thanks @sterliakov! - Fixed #6621: Improved handling of multiple adjacent line suppressions. Biome now handles such suppressions separately, tracking whether each one is used. -
#6700
cdd6e17
Thanks @denbezrukov! - Fixed #6680: Biome incorrectly formatted container-style queries by inserting misplaced spaces.@container style (--responsive: true) {}@container style(--responsive: true) {} -
#6709
ecf3954
Thanks @dyc3! - Fixed #6038: Fixed a false positive innoShadow
where a function parameter in a type definition was erroneously flagged as a violation. -
#6593
a4acbb7
Thanks @arendjr! - Type inference is now able to handle ternary conditions in expressions.Examples
const condition = Math.random() > -1; // Always true, but dynamic to linter// We now detect that this may return a `Promise`.condition ? Promise.reject("ternary bypass") : null;// On the other hand, we know the following is never a `Promise`:const alwaysFalsy = 0;alwaysFalsy ? Promise.reject("ternary bypass") : null; -
#6428
4b501d3
Thanks @siketyan! - AddedMemoryFileSystem
to the WASM API.You can now insert a file from your JS code:
import { MemoryFileSystem, Workspace } from "@biomejs/wasm-web";const fs = new MemoryFileSystem();const workspace = Workspace.withFileSystem(fs);fs.insert("/index.js", new TextEncoder().encode("let foo = 1;"));fs.remove("/index.js"); -
#6594
626d4a1
Thanks @ematipico! - Fixed #6528: Biome didn’t return the correct output when applyingsource.fixAll.biome
inside Astro/Vue/Svelte files that contained safe fixed.
2.0.6
Patch Changes
-
#6557
fd68458
Thanks @ematipico! - Fixed a bug where Biome didn’t provide all the available code actions when requested by the editor. -
#6511
72623fa
Thanks @Conaclos! - Fixed #6492. TheorganizeImports
assist action no longer duplicates a comment at the start of the file when:BLANK_LINE:
precedes the first import group. -
#6557
fd68458
Thanks @ematipico! - Fixed #6287 where Biome Language Server didn’t adhere to thesettings.requireConfiguration
option when pulling diagnostics and code actions. Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities. -
#6551
0b63b1d
Thanks @Conaclos! - Fixed #6536.useSortedKeys
no longer panics in some edge cases where object spreads are involved. -
#6503
9a8fe0f
Thanks @ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled. -
#6565
e85761c
Thanks @daivinhtran! - Fixed #4677: Now thenoUnusedImports
rule won’t produce diagnostics for types used in JSDoc comment of exports. -
#6166
b8cbd83
Thanks @mehm8128! - Added the nursery rule noExcessiveLinesPerFunction. This rule restrict a maximum number of lines of code in a function body.The following code is now reported as invalid when the limit of maximum lines is set to 2:
function foo() {const x = 0;const y = 1;const z = 2;}The following code is now reported as valid when the limit of maximum lines is set to 3:
const bar = () => {const x = 0;const z = 2;}; -
#6553
5f42630
Thanks @denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses@starting-style
when it’s used inside other at-rules. The following example doesn’t raise an error anymore:@layer my-demo-layer {@starting-style {div.showing {background-color: red;}}} -
#6458
05402e3
Thanks @ematipico! - Fixed an issue where the ruleuseSemanticElements
used the incorrect range when positioning suppression comments. -
#6560
6d8a6b9
Thanks @siketyan! - Fixed #6559: the error message on detected a large file was outdated and referred a removed configuration optionfiles.ignore
. -
#6458
05402e3
Thanks @ematipico! - Fixed #6384. The ruleuseAltText
now emits a diagnostic with a correct range, so suppression comments can work correctly. -
#6518
7a56288
Thanks @wojtekmaj! - Fixed #6508, where the rulenoUselessFragments
incorrectly flagged Fragments containing HTML entities as unnecessary. -
#6517
c5217cf
Thanks @arendjr! - Fixed #6515. When using theextends
field to extend a configuration from an NPM package, we now accept the condition names"biome"
and"default"
for exporting the configuration in thepackage.json
.This means that where previously your
package.json
had to contain an export declaration similar to this:{"exports": {".": "./biome.json"}}You may now use one of these as well:
{"exports": {".": {"biome": "./biome.json"}}}Or:
{"exports": {".": {"default": "./biome.json"}}} -
#6219
a3a3715
Thanks @huangtiandi1999! - Added new nursery rulenoUnassignedVariables
, which disallowslet
orvar
variables that are read but never assigned.The following code is now reported as invalid:
let x;if (x) {console.log(1);}The following code is now reported as valid:
let x = 1;if (x) {console.log(1);} -
#6395
f62e748
Thanks @mdevils! - Added the new nursery rulenoImplicitCoercion
, which disallows shorthand type conversions in favor of explicit type conversion functions.Example (Invalid): Boolean conversion using double negation:
!!foo;!!(foo + bar);Example (Invalid): Number conversion using unary operators:
+foo;-(-foo);foo - 0;foo * 1;foo / 1;Example (Invalid): String conversion using concatenation:
"" + foo;foo + "";`` + foo;foo += "";Example (Invalid): Index checking using bitwise NOT:
~foo.indexOf(1);~foo.bar.indexOf(2);Example (Valid): Using explicit type conversion functions:
Boolean(foo);Number(foo);String(foo);foo.indexOf(1) !== -1; -
#6544
f28b075
Thanks @daivinhtran! - Fixed #6536. Now the rulenoUselessFragments
produces diagnostics for a top-level useless fragment that is in a return statement. -
#6320
5705f1a
Thanks @mdevils! - Added the new nursery ruleuseUnifiedTypeSignature
, which disallows overload signatures that can be unified into a single signature.Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.
Example (Invalid): Overload signatures that can be unified:
function f(a: number): void;function f(a: string): void;interface I {a(): void;a(x: number): void;}Example (Valid): Unified signatures:
function f(a: number | string): void {}interface I {a(x?: number): void;}Example (Valid): Different return types cannot be merged:
interface I {f(): void;f(x: number): number;} -
#6545
2782175
Thanks @ematipico! - Fixed #6529, where the Biome Language Server would emit an error when the user would open a file that isn’t part of its workspace (node_modules
or external files). Now the language server doesn’t emit any errors and it exits gracefully. -
#6524
a27b825
Thanks @vladimir-ivanov! - Fixed #6500: TheuseReadonlyClassProperties
rule now correctly marks class properties asreadonly
when they are assigned in a constructor, setter or method, even if the assignment occurs inside an if or else block.The following code is now correctly detected by the rule:
class Price {#price: string;@Input()set some(value: string | number) {if (value === undefined ||value === null ||value === "undefined" ||value === "null" ||Number.isNaN(value)) {this.#price = "";} else {this.#price = "" + value;}}} -
#6355
e128ea9
Thanks @anthonyshew! - Added a new nursery rulenoAlert
that disallows the use ofalert
,confirm
andprompt
.The following code is deemed incorrect:
alert("here!"); -
#6548
37e9799
Thanks @ematipico! - Fixed #6459, where the Biome LSP was not taking into account the correct settings when applyingsource.fixAll.biome
code action.
2.0.5
Patch Changes
-
#6461
38862e6
Thanks @ematipico! - Fixed #6419, a regression where stdin mode would create a temporary new file instead of using the one provided by the user. This was an intended regression.Now Biome will use the file path passed via
--std-file-path
, and apply the configuration that matches it. -
#6480
050047f
Thanks @Conaclos! - Fixed #6371. useNamingConvention now checks the string case of objects’ property shorthand. -
#6477
b98379d
Thanks @ematipico! - Fixed an issue where Biome formatter didn’t format consistently CSS value separated by commas..font-heading {font-feature-settings: var(--heading-salt), var(--heading-ss06),var(--heading-ss11), var(--heading-cv09), var(--heading-liga),var(--heading-calt);font-feature-settings:var(--heading-salt), var(--heading-ss06), var(--heading-ss11),var(--heading-cv09), var(--heading-liga), var(--heading-calt);} -
#6248
ec7126c
Thanks @fireairforce! - Fixed grit pattern matching for different kinds of import statements.The grit pattern
import $imports from "foo"
will match the following code:import bar from "foo";import { bar } from "foo";import { bar, baz } from "foo";
2.0.4
Patch Changes
- #6450
7472d9e
Thanks @ematipico! - Fixed an issue where the binary wasn’t correctly mapped.
Copyright (c) 2023-present Biome Developers and Contributors.