@biomejs/biome
Advanced tools
Changelog
v1.9.1 (2024-09-15)
useEditorConfig
now loads the editorconfig when running biome ci
#3864. Contributed by @dyc3
Revert #3731 to fix broken quick fixes and code actions. Contributed by @nhedger
useSemanticElements now ignores alert
and alertdialog
roles (3858). Contributed by @Conaclos
noUndeclaredDependencies now ignores @/
imports and recognizes type imports from Definitely Typed and bun
imports. Contributed by @Conaclos
Changelog
v1.8.3 (2024-06-27)
Fix #3104 by suppressing node warnings when using biome migrate
. Contributed by @SuperchupuDev
Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @Sec-ant
nursery/useDeprecatedReason
rule. Contributed by @vohoanglong0107.useImportExtensions
rule. Contributed by @drdaemosuseConsistentArrayType
and useShorthandArrayType
now ignore Array
in the extends
and implements
clauses. Fix #3247. Contributed by @Conaclospackage.json
. Contributed by @ematipicouseArrowFunction
rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @Sec-antEnhance tailwind sorting lint rule #1274 with variant support.
Every preconfigured variant is assigned a weight
that concurs on establishing the output sorting order.
Since nesting variants on the same utility class is possible, the resulting weight
is the Bitwise XOR of all the variants weight for that class.
Dynamic variants (e.g. has-[.custom-class]
, group-[:checked]
) are also supported and they take the weight
of their base variant name the custom value attached (e.g. has-[.custom-class]
takes has
weight).
Arbitrary variants (e.g. [&nth-child(2)]
) don't have a weight assigned and they are placed after every known variant.
Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
Screen variants (e.g. sm:
, max-md:
, min-lg:
) are not supported yet.
Contributed by @lutaok
Changelog
v1.8.2 (2024-06-20)
biome migrate
and thus choke the parser. Contributed by @Sec-antReword the reporter message No fixes needed
to No fixes applied
.
The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:
Checked 2 files in <TIME>. No fixes needed.
Found 2 errors.
The new message suits better in these cases.
Contributed by @Sec-ant
Don't conceal previous overrides (#3176).
Previously, each override inherited the unset configuration of the base configuration. This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.
For example, in the next example, noDebugger
was disabled for the index.js
file.
{
"linter": {
"rules": {
"suspicious": { "noDebugger": "off" }
}
},
"overrides": [
{
"include": ["index.js"],
"linter": {
"rules": {
"suspicious": { "noDebugger": "warn" }
}
}
}, {
"include": ["index.js"],
"linter": {
"rules": {
"suspicious": { "noDoubleEquals": "off" }
}
}
}
]
}
The rule is now correctly enabled for the index.js
file.
Contributed by @Conaclos
v1.8.0
Add nursery/noShorthandPropertyOverrides. #2958 Contributed by @neokidev
Fix [#3084] false positive by correctly recognize parenthesized return statement. Contributed by @unvalley
useImportExtensions now suggests a correct fix for import '.'
and import './.'
. Contributed by @minht11
Fix useDateNow false positive when new Date object has arguments new Date(0).getTime()
. Contributed by @minht11.
The noUnmatchableAnbSelector
rule is now able to catch unmatchable an+b
selectors like 0n+0
or -0n+0
. Contributed by @Sec-ant.
The useHookAtTopLevel
rule now recognizes properties named as hooks like foo.useFoo()
. Contributed by @ksnyder9801
Fix #3092, prevent warning for Custom properties (--*)
. Contributed by @chansuke
Fix a false positive in the useLiteralKeys
rule. (#3160)
This rule now ignores the following kind of computed member name:
const a = {
[`line1
line2`]: true,
};
Contributed by @Sec-ant
The noUnknownProperty rule now ignores the composes
property often used in css modules. #3000 Contributed by @chansuke
Fix false positives of the useExhaustiveDependencies rule.
The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:
import { useMemo } from "react";
function MyRecursiveComponent() {
// MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
const children = useMemo(() => <MyRecursiveComponent />, []);
return <div>{children}</div>;
}
Also, export default function
and export default class
are considered stable now because they can only appear at the top level of a module.
Contributed by @Sec-ant
Fix missing withDefaults
macro in vue files for globals variables. Contributed by @Shyam-Chen
Changelog
v1.8.1 (2024-06-10)
--staged
or --changed
options. Contributed by @unvalleyindentWidth
. Contributed by @ematipicoThe noEmptyBlock
css lint rule now treats empty blocks containing comments as valid ones. Contributed by @Sec-ant
useLiteralKeys no longer reports quoted member names (#3085).
Previously useLiteralKeys reported quoted member names that can be unquoted. For example, the rule suggested the following fix:
- const x = { "prop": 0 };
+ const x = { prop: 0 };
This conflicted with the option quoteProperties of our formatter.
The rule now ignores quoted member names.
Contributed by @Conaclos
noEmptyInterface now ignores empty interfaces in ambient modules (#3110). Contributed by @Conaclos
noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#3135).
Previously, arg
was reported as unused in a constructor type like:
export type Classlike = new (arg: unknown) => string;
Contributed by @Conaclos
noStringCaseMismatch now ignores escape sequences (#3134).
The following code is no longer reported by the rule:
s.toUpperCase() === "\u001b";
Contributed by @Conaclos