@biomejs/biome
Advanced tools
Changelog
v1.9.4 (2024-10-17)
Improved the message for unused suppression comments. Contributed by @dyc3
Fix #4228, where the rule a11y/noInteractiveElementToNoninteractiveRole
incorrectly reports a role
for non-interactive elements. Contributed by @eryue0220
noSuspiciousSemicolonInJsx
now catches suspicious semicolons in React fragments. Contributed by @vasucp1207
The --summary
reporter now reports parsing diagnostics too. Contributed by @ematipico
Improved performance of GritQL queries by roughly 25-30%. Contributed by @arendjr
Biome no longer crashes when it encounters a string that contain a multibyte character (#4181).
This fixes a regression introduced in Biome 1.9.3 The regression affected the following linter rules:
nursery/useSortedClasses
nursery/useTrimStartEnd
style/useTemplate
suspicious/noMisleadingCharacterClass
Contributed by @Conaclos
Fix #4190, where the rule noMissingVarFunction
wrongly reported a variable as missing when used inside a var()
function that was a newline. Contributed by @ematipico
Fix #4041. Now the rule useSortedClasses
won't be triggered if className
is composed only by inlined variables. Contributed by @ematipico
useImportType and useExportType now report useless inline type qualifiers (#4178).
The following fix is now proposed:
- import type { type A, B } from "";
+ import type { A, B } from "";
- export type { type C, D };
+ export type { C, D };
Contributed by @Conaclos
useExportType now reports ungrouped export from
.
The following fix is now proposed:
- export { type A, type B } from "";
+ export type { A, B } from "";
Contributed by @Conaclos
noVoidTypeReturn now accepts void
expressions in return position (#4173).
The following code is now accepted:
function f(): void {
return void 0;
}
Contributed by @Conaclos
noUselessFragments now correctly handles fragments containing HTML escapes (e.g.
) inside expression escapes { ... }
(#4059).
The following code is no longer reported:
function Component() {
return (
<div key={index}>{line || <> </>}</div>
)
}
Contributed by @fireairforce
noUnusedFunctionParameters and noUnusedVariables no longer reports a parameter as unused when another parameter has a constructor type with the same parameter name (#4227).
In the following code, the name
parameter is no longer reported as unused.
export class Foo {
bar(name: string, _class: new (name: string) => any) {
return name
}
}
Contributed by @Conaclos
noUndeclaredDependencies now accepts dependency names with dots. Contributed by @Conaclos
useFilenamingConvention now correctly handles renamed exports (#4254).
The rule allows the filename to be named as one of the exports of the module.
For instance, the file containing the following export can be named Button
.
class Button {}
export { Button }
The rule now correctly handles the renaming of an export.
For example, the file containing the following export can only be named Button
.
Previously the rule expected the file to be named A
.
class A {}
export { A as Button }
Contributed by @Conaclos
useConsistentMemberAccessibility now ignore private class members such as #property
(#4276). Contributed by @Conaclos
noUnknownFunction correctly handles calc-size
function (#4212).
The following code calc-size
is no longer reported as unknown:
.a { height: calc-size(0px); }
Contributed by @fireairforce
useNamingConvention now allows configuring conventions for readonly index signatures.
Contributed by @sepruko
The CSS parser now accepts more emoji in identifiers (#3627).
Browsers accept more emoji than the standard allows. Biome now accepts these additional emojis.
The following code is now correctly parsed:
p {
--β¨-color: red;
color: var(--β¨-color);
}
Contributed by @Conaclos
Add support for parsing typescript's resolution-mode
in Import Types(#2115)
export type Fs = typeof import('fs', { with: { 'resolution-mode': 'import' } });
export type TypeFromRequire =
import("pkg", { with: { "resolution-mode": "require" } }).TypeFromRequire;
export type TypeFromImport =
import("pkg", { with: { "resolution-mode": "import" } }).TypeFromImport;
Contributed by @fireairforce
Changelog
v1.9.3 (2024-10-01)
GritQL queries that match functions or methods will now match async functions or methods as well.
If this is not what you want, you can capture the async
keyword (or its absence) in a metavariable and assert its emptiness:
$async function foo() {} where $async <: .
Contributed by @arendjr
Fix #4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @arendjr
Fix #4102. Now the CLI command lint
doesn't exit with an error code when using --write
/--fix
. Contributed by @ematipico
noLabelWithoutControl
options where incorrectly marked as mandatory. Contributed by @ematipicoFix #3924 where GraphQL formatter panics in block comments with empty line. Contributed by @vohoanglong0107
Fix a case where raw values inside url()
functions weren't properly trimmed.
.value {
- background: url(
- whitespace-around-string
- );
+ background: url(whitespace-around-string);
}
Contributed by @ematipico
Fixed #4076, where a media query wasn't correctly formatted:
.class {
- @media (1024px <= width <=1280px) {
+ @media (1024px <= width <= 1280px) {
color: red;
}
}
Contributed by @blaze-d83
Add noDescendingSpecificity. Contributed by @tunamaguro
Add noNestedTernary. Contributed by @kaykdm
Add noTemplateCurlyInString. Contributed by @fireairforce
Add noOctalEscape. Contributed by @fireairforce
Add an option reportUnnecessaryDependencies
to useExhaustiveDependencies.
Defaults to true. When set to false, errors will be suppressed for React hooks that declare dependencies but do not use them.
Contributed by @simon-paris
Add an option reportMissingDependenciesArray
to useExhaustiveDependencies. Contributed by @simon-paris
noControlCharactersInRegex no longer panics on regexes with incomplete escape sequences. Contributed by @Conaclos
noMisleadingCharacterClass no longer reports issues outside of character classes.
The following code is no longer reported:
/[a-z]π/;
Contributed by @Conaclos
noUndeclaredDependencies no longer reports Node.js builtin modules as undeclared dependencies.
The rule no longer reports the following code:
import * as fs from "fs";
Contributed by @Conaclos
noUnusedVariables no longer panics when suggesting the renaming of a variable at the start of a file (#4114). Contributed by @Conaclos
noUselessEscapeInRegex no longer panics on regexes that start with an empty character class. Contributed by @Conaclos
noUselessStringConcat no longer panics when it encounters malformed code. Contributed by @Conaclos
noUnusedFunctionParameters no longer reports unused parameters inside an object pattern with a rest parameter.
In the following code, the rule no longer reports a
as unused.
function f({ a, ...rest }) {
return rest;
}
This matches the behavior of noUnusedVariables.
Contributed by @Conaclos
useButtonType no longer reports dynamically created button with a valid type (#4072).
The following code is no longer reported:
React.createElement("button", { type: "button" }, "foo")
Contributed by @Conaclos
useSemanticElements now ignores elements with the img
role (#3994).
MDN recommends using role="img"
for grouping images or creating an image from other elements.
The following code is no longer reported:
<div role="img" aria-label="That cat is so cute">
<p>🐈 😂</p>
</div>
Contributed by @Conaclos
useSemanticElements now ignores alert
and alertdialog
roles (#3858). Contributed by @Conaclos
noUselessFragments don't create invaild JSX code when Fragments children contains JSX Expression and in a LogicalExpression. Contributed by @fireairforce
Changelog
v1.9.2 (2024-09-19)
Added support for custom GritQL definitions, including:
Contributed by @arendjr
contains
queries to report false positives when the matched
node appeared inside a sibling node. Contributed by @arendjrFix #3923. Now the .editorconfig
is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered.
Plus, the Biome LSP now watches for any change to the .editorconfig
, and updates the formatting settings.
Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico
Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.
This means that the code actions are pulled by the client only when the editor enables quickfix.biome
, source.organizeImports.biome
and source.fixAll.biome
.
Now, if you enable organizeImports.enabled: true
in the biome.json
, and then you configure your editor with the following code action source.organizeImports.biome: false
, the editor won't sort the imports.
Contributed by @ematipico
noLabelWithoutControl now accept JSX expression as label value (#3875). Contributed by @Conaclos
useFilenamingConvention no longer suggests names with a disallowed case (#3952). Contributed by @Conaclos
useFilenamingConvention now recognizes file names starting with ASCII digits as lowercase (#3952).
Thus, 2024-09-17-filename
, 2024_09_17_filename
and 20240917FileName
are in kebab-case
, snake_case
, and camelCase
respectively.
Contributed by @Conaclos
useFilenamingConvention now applies the configured formats to the file extensions (#3650). Contributed by @Conaclos
useStrictMode now reports Script files with some directives, but without the use strict
directive. Contributed by @Conaclos
The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos
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.9.0 (2024-09-12)
Add --graphql-linter-enabled
option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipico
New EXPERIMENTAL search
command. The search command allows you to search a Biome project using GritQL syntax.
GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.
While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.
For now, the search
command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!
Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.
biome search '`console.log($message)`' # find all `console.log` invocations
Contributed by @arendjr and @BackupMiles
The option --max-diagnostics
now accept a none
value, which lifts the limit of diagnostics shown. Contributed by @ematipico
Add a new reporter --reporter=gitlab
, that emits diagnostics for using the GitLab Code Quality report.
[
{
"description": "Use === instead of ==. == is only allowed when comparing against `null`",
"check_name": "lint/suspicious/noDoubleEquals",
"fingerprint": "6143155163249580709",
"severity": "critical",
"location": {
"path": "main.ts",
"lines": {
"begin": 4
}
}
}
]
Contributed by @NiclasvanEyk
Add new options to the lsp-proxy
and start
commands:
--log-path
: a directory where to store the daemon logs. The commands also accepts the environment variable BIOME_LOG_PATH
.--log-prefix-name
: a prefix that's added to the file name of the logs. It defaults to server.log
. The commands also accepts the environment variable BIOME_LOG_PREFIX_NAME
.@Contributed by @ematipico
When a --reporter
is provided, and it's different from the default one, the value provided by via --max-diagnostics
is ignored and the limit is lifted. Contributed by @ematipico
biome init
now generates a new config file with more options set.
This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
Contributed by @Conaclos
The --verbose
flag now reports the list of files that were evaluated, and the list of files that were fixed.
The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.
VERBOSE ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
βΉ Files processed:
- biome/biome.json
- biome/packages/@biomejs/cli-win32-arm64/package.json
- biome/packages/tailwindcss-config-analyzer/package.json
VERBOSE ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
βΉ Files fixed:
- biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts
Contributed by @ematipico
Allow passing nursery
to the --only
and --skip
filters.
The --only
option allows you to run a given rule or rule group.
The --skip
option allows you to skip the execution of a given group or a given rule.
Previously, it was not possible to pass nursery
.
This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.
Contributed by @Conaclos
The CLI now returns an error code when calling a command in stdin
mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of 1
because the lint
command triggers some lint rules:
echo "let x = 1" | biome lint --stdin-file-path=stdin.js
Contributed by @ematipico
biome lint --write
now takes --only
and --skip
into account (#3470). Contributed by @Conaclos
Fix #3368, now the reporter github
tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipico
Fix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219
Migrating from Prettier or ESLint no longer overwrite the overrides
field from the configuration (#3544). Contributed by @Conaclos
Fix JSX expressions for noAriaHiddenOnFocusable
(#3708). Contributed by @anthonyshew
Fix edge case for <canvas>
elements that use role="img"
(#3728). Contributed by @anthonyshew
Fix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico
Allow aria-label
on heading to prevent useHeadingContent
diagnostic (#3767). Contributed by @anthonyshew
Fix edge case #3791 for rule noFocusedTests
being used with non-string-like expressions (#3793). Contributed by @h-a-n-a
Fix optional ARIA properties for role="separator"
in useAriaPropsForRole
(#3856). Contributed by @anthonyshew
Add support for loading configuration from .editorconfig
files (#1724).
Configuration supplied in .editorconfig
will be overridden by the configuration in biome.json
. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json
:
{
"formatter": {
"useEditorconfig": true
}
}
Contributed by @dyc3
overrides
from an extended configuration is now merged with the overrides
of the extension.
Given the following shared configuration biome.shared.json
:
{
"overrides": [
{
"include": ["**/*.json"],
// ...
}
]
}
and the following configuration:
{
"extends": ["./biome.shared.json"],
"overrides": [
{
"include": ["**/*.ts"],
// ...
}
]
}
Previously, the overrides
from biome.shared.json
was overwritten.
It is now merged and results in the following configuration:
{
"extends": ["./biome.shared.json"],
"overrides": [
{
"include": ["**/*.json"],
// ...
},
{
"include": ["**/*.ts"],
// ...
}
]
}
Contributed by @Conaclos
Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
Fix #3696, where biome.jsonc
was incorrectly parsed with incorrect options. Contributed by @ematipico
The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json
:
{
- "css": {
- "formatter": {
- "enabled": true
- }
- }
}
Contributed by @ematipico
Add parentheses for nullcoalescing in ternaries.
This change aligns on Prettier 3.3.3. This adds clarity to operator precedence.
- foo ? bar ?? foo : baz;
+ foo ? (bar ?? foo) : baz;
Contributed by @Conaclos
Keep the parentheses around infer ... extends
declarations in type unions and type intersections (#3419). Contributed by @Conaclos
Keep parentheses around a yield
expression inside a type assertion.
Previously, Biome removed parentheses around some expressions that require them inside a type assertion. For example, in the following code, Biome now preserves the parentheses.
function* f() {
return <T>(yield 0);
}
Contributed by @Conaclos
Remove parentheses around expressions that don't need them inside a decorator.
Biome now matches Prettier in the following cases:
class {
- @(decorator)
+ @decorator
method() {}
},
class {
- @(decorator())
+ @decorator()
method() {}
},
class {
@(decorator?.())
method() {}
},
Contributed by @Conaclos
Keep parentheses around objects preceded with a @satisfies
comment.
In the following example, parentheses are no longer removed.
export const PROPS = /** @satisfies {Record<string, string>} */ ({
prop: 0,
});
Contributed by @Conaclos
New rules are incubated in the nursery group. Once stable, we promote them to a stable group.
The following CSS rules are promoted:
The following JavaScript rules are promoted:
correctness/noInvalidNewBuiltin
is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.style/useSingleCaseStatement
is deprecated. Use correctness/noSwitchDeclarations instead.suspicious/noConsoleLog
is deprecated. Use suspicious/noConsole instead.Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrregularWhitespace. Contributed by @DerTimonius
Rename nursery/noUnknownSelectorPseudoElement
to nursery/noUnknownPseudoElement
. Contributed by @togami2864
The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json
:
{
- "css": {
- "linter": {
- "enabled": true
- }
- }
}
Contributed by @ematipico
The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @Conaclos
noBlankTarget now supports an array of allowed domains.
The following configuration allows example.com
and example.org
as blank targets.
"linter": {
"rules": {
"a11y": {
"noBlankTarget": {
"level": "error",
"options": {
"allowDomains": ["example.com", "example.org"]
}
}
}
}
}
Contributed by @Jayllyz
noConsole now accepts an option that specifies some allowed calls on console
. Contributed by @Conaclos
Add an ignoreNull
option for noDoubleEquals.
By default the rule allows loose comparisons against null
.
The option ignoreNull
can be set to false
for reporting loose comparison against null
.
Contributed by @peaBerberian.
noDuplicateObjectKeys now works for JSON and JSONC files. Contributed by @ematipico
noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.
In the following code, A
is reported as use before its declaration.
enum E {
B = A << 1,
A = 1,
}
Contributed by @Conaclos
noNodejsModules now ignores imports of a package which has the same name as a Node.js module. Contributed by @Conaclos
noNodejsModules now ignores type-only imports (#1674).
The rule no longer reports type-only imports such as:
import type assert from "assert";
import type * as assert2 from "assert";
Contributed by @Conaclos
noRedundantUseStrict no longer reports "use strict"
directives when the package.json
marks explicitly the file as a script using the field "type": "commonjs"
. Contributed by @ematipico
noStaticOnlyClass no longer reports a class that extends another class (#3612). Contributed by @errmayank
noUndeclaredVariables no longer reports a direct reference to an enum member (#2974).
In the following code, the A
reference is no longer reported as an undeclared variable.
enum E {
A = 1,
B = A << 1,
}
Contributed by @Conaclos
noUndeclaredVariables recognized Svelte 5 runes in Svelte components and svelte files.
Svelte 5 introduced runes.
The rule now recognizes Svelte 5 runes in files ending with the .svelte
, .svelte.js
or .svelte.ts
extensions.
Contributed by @Conaclos
noUnusedVariables now checks TypeScript declaration files.
This allows to report a type that is unused because it isn't exported. Global declarations files (declarations files without exports and imports) are still ignored.
Contributed by @Conaclos
useFilenamingConvention now supports unicase letters.
unicase letters have a single case: they are neither uppercase nor lowercase.
Biome now accepts filenames in unicase.
For example, the filename μλ
νμΈμ
is now accepted.
We still reject a name that mixes unicase characters with lowercase or uppercase characters.
For example, the filename Aμλ
νμΈμ
is rejected.
This change also fixes #3353. Filenames consisting only of numbers are now accepted.
Contributed by @Conaclos
useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#3465).
Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as [...slug].js
and [[...slug]].js
.
Biome now recognizes this syntax. slug
must contain only alphanumeric characters.
Contributed by @Conaclos
useExportType no longer reports empty export
(#3535).
An empty export {}
allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.
While export type {}
is valid, it is more common to use export {}
.
Users may find it confusing that the linter asks them to convert it to export type {}
.
Also, a bundler should be able to remove export {}
as well as export type {}
.
So it is not so useful to report export {}
.
Contributed by @Conaclos
noControlCharactersInRegex now corretcly handle \u
escapes in unicode-aware regexes.
Previously, the rule didn't consider regex with the v
flags as unicode-aware regexes.
Moreover, \uhhhh
was not handled in unicode-aware regexes.
Contributed by @Conaclos
noControlCharactersInRegex now reports control characters and escape sequence of control characters in string regexes. Contributed by @Conaclos
noExcessiveNestedTestSuites
: fix an edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3
noExtraNonNullAssertion
no longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @Conaclos
noMultipleSpacesInRegularExpressionLiterals now correctly provides a code fix when Unicode characters are used. Contributed by @Conaclos
noRedeclare no longer report redeclartions for lexically scoped function declarations #3664.
In JavaScript strict mode, function declarations are lexically scoped: they cannot be accessed outside the block where they are declared.
In non-strict mode, function declarations are hoisted to the top of the enclosing function or global scope.
Previously Biome always hoisted function declarations. It now takes into account whether the code is in strict or non strict mode.
Contributed by @Conaclos
noUndeclaredDependencies now ignores self package imports.
Given teh following package.json
:
{
"name": "my-package",
"main": "index.js"
}
The following import is no longer reported by the rule:
import * as mod from "my-package";
Contributed by @Conaclos
Fix [#3149] crashes that occurred when applying the noUselessFragments
unsafe fixes in certain scenarios. Contributed by @unvalley
noRedeclare no longer reports a variable named as the function expression where it is declared. Contributed by @Conaclos
useAdjacentOverloadSignatures
no longer reports a #private
class member and a public class member that share the same name (#3309).
The following code is no longer reported:
class C {
#f() {}
g() {}
f() {}
}
Contributed by @Conaclos
useAltText n olonger requests alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown
useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos
useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).
Previously the following code led useNamingConvention
to suggest an empty fix.
The rule no longer provides a fix for this case.
type AAb = any
Contributed by @Conaclos
useNamingConvention no longer provides fixes for global TypeScript declaration files.
Global TypeScript declaration files have no epxorts and no imports. All the declared types are available in all files of the project. Thus, it is not safe to propose renaming only in the declaration file.
Contributed by @Conaclos
useSortedClasses lint error with Template literals (#3394). Contributed by @hangaoke1
useValidAriaValues now correctly check property types (3748).
Properties that expect a string now accept arbitrary text. An identifiers can now be made up of any characters except ASCII whitespace. An identifier list can now be separated by any ASCII whitespace.
Contributed by @Conaclos
The JSON parser now allows comments in turbo.json
and jest.config.json
. Contributed by @Netail and @Conaclos
The JSON parser now allows comments in files with the .json
extension under the .vscode
and .zed
directories.
Biome recognizes are well known JSON files that allows comments and/or trailing commas.
Previously, Biome did not recognize JSON files under the .vscode
and the .zed
directories as JSON files that allow comments.
You had to configure Biome to recognize them:
{
"overrides": [
{
"include": ["**/.vscode/*.json", "**/.zed/*.json"],
"json": { "parser": { "allowComments": true } }
}
]
}
This override is no longer needed!
Note that JSON files under the .vscode
and the .zed
directories don't accept trailing commas.
Contributed by @Conaclos
The CSS parser now accepts emoji in identifiers (3627).
The following code is now correctly parsed:
p {
--π₯-color: red;
color: var(--π₯-color);
}
Contributed by @Conaclos
Fix #3287 nested selectors with pseudo-classes. Contributed by @denbezrukov
Fix #3349 allow CSS multiple ampersand support. Contributed by @denbezrukov
.class {
&& {
color: red;
}
}
Fix #3410 by correctly parsing break statements containing keywords.
out: while (true) {
break out;
}
Contributed by @ah-yu
Fix #3464 by enabling JSX in .vue
files that use the lang='jsx'
or lang='tsx'
attribute. Contributed by @ematipico