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

Enhancements

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

Bug fixes

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

Configuration

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

Editors

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

Formatter

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

Linter

Promoted rules

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:

Deprecated rules

correctness/noInvalidNewBuiltin is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.
style/useSingleCaseStatement is deprecated. Use correctness/noSwitchDeclarations instead.
suspicious/noConsoleLog is deprecated. Use suspicious/noConsole instead.

New features

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

Enhancements

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

Bug fixes

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

Parser

Enhancements

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

Bug fixes

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

1.8.4-nightly.7aaf0ce

Diff

dominionl

published 1.8.4-nightly.7aaf0ce • 4 months ago

1.8.4-nightly.d079e53

Diff

dominionl

published 1.8.4-nightly.d079e53 • 4 months ago

1.8.4-nightly.bd1d0c6

Diff

dominionl

published 1.8.4-nightly.bd1d0c6 • 5 months ago

1.8.4-nightly.a579bf7

Diff

dominionl

published 1.8.4-nightly.a579bf7 • 6 months ago

1.8.3

Diff

dominionl

published 1.8.3 • 6 months ago

Changelog

Source

v1.8.3 (2024-06-27)

CLI

Bug fixes

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

Parser

Bug fixes

Implement CSS unicode range. Contributed by @denbezrukov

Formatter

Bug fixes

Fix #3184 CSS formatter converts custom identifiers to lowercase. Contributed by @denbezrukov
Fix #3256 constant crashes when editing css files #3256. Contributed by @denbezrukov

Linter

New features

Add nursery/useDeprecatedReason rule. Contributed by @vohoanglong0107.
Add nursery/noExportedImports. Contributed by @Conaclos

Enhancements

Implement suggestedExtensions option for useImportExtensions rule. Contributed by @drdaemos

Bug fixes

useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @Conaclos
Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @ematipico
The code action of the useArrowFunction 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-ant

Enhancements

Enhance 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

1.8.2

Diff

dominionl

published 1.8.2 • 6 months ago

Changelog

Source

v1.8.2 (2024-06-20)

CLI

Bug fixes

Fix #3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @ematipico
Fix #3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @Sec-ant
Fix #3232 by correctly using the colors set by the user. Contributed by @ematipico

Enhancement

Reword 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

Configuration

Bug fixes

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

Formatter

Bug fixes

Fix #3103 by correctly resolving CSS formatter options. Contributed by @ah-yu
Fix #3192 don't add an extra whitespace within :has. Contributed by @denbezrukov

JavaScript APIs

Bug fixes

Fix a regression introduced by the release of v1.8.0

Linter

New features

Add nursery/noSubstr. Contributed by @chansuke
Add nursery/useConsistentCurlyBraces. Contributed by @dyc3
Add nursery/useValidAutocomplete. Contributed by @unvalley

Enhancements

Add a code action for noUselessCatch. Contributed by @chansuke

Bug fixes

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

Parser

Bug fixes

Fix CSS modules settings mapping. Contributed by @denbezrukov

1.8.1

Diff

dominionl

published 1.8.1 • 7 months ago

Changelog

Source

v1.8.1 (2024-06-10)

CLI

Bug fixes

Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @unvalley
Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @uncenter

Configuration

Bug fixes

Fix #3067, by assigning the correct default value to indentWidth. Contributed by @ematipico

Formatter

Bug fixes

Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @denbezrukov
Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @denbezrukov
Fix the formatting of CSS grid layout properties. Contributed by @denbezrukov

Linter

New features

Add noUnknownPseudoClass. Contributed by @tunamaguro

Bug fixes

The 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

Parser

Bug fixes

Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by @denbezrukov
Fix #3055 CSS: Layout using named grid lines is now correctly parsed. Contributed by @denbezrukov
Fix #3091. Allows the parser to handle nested style rules and at-rules properly, enhancing the parser's compatibility with the CSS Nesting Module. Contributed by @denbezrukov

1.8.0

Diff

dominionl

published 1.8.0 • 7 months ago

Changelog

Source

1.8.0 (2024-06-04)

Analyzer

New features

Allow suppression comments to suppress individual instances of rules. This is used for the lint rule useExhaustiveDependencies, which is now able to suppress specific dependencies. Fixes #2509. Contributed by @arendjr

Enhancements

Assume Astro object is always a global when processing .astro files. Contributed by @minht11
Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @dyc3

CLI

New features

New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.
```
biome clean
```
Add two new options --only and --skip to the command biome lint (#58).

The --only option allows you to run a given rule or rule group, For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules. If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.
```
biome lint --only=style/useNamingConvention --only=style/noInferrableTypes
```
Passing a group does not change the severity level of the rules in the group. All the disabled rules in the group will remain disabled. To ensure that the group is run, the recommended field of the group is enabled. The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

The --skip option allows you to skip the execution of a given group or a given rule. For example, the following command skips the style group and the suspicious/noExplicitAny rule.
```
biome lint --skip=style --skip=suspicious/noExplicitAny
```
You can also use --only and --skip together. --skip overrides --only. The following command executes only the rules from the style group, but the style/useNamingConvention rule.
```
biome lint --only=style --skip=style/useNamingConvention
```
These options are compatible with other options such as --write (previously --apply), and --reporter.

Contributed by @Conaclos
Add new command biome clean. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tends log many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the biome-logs folder could become quite heavy. Contributed by @ematipico
Add support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.

If you don't have a configuration file, you can enable these features with --css-formatter-enabled and --css-linter-enabled:
```
biome check --css-formatter-enabled=true --css-linter-enabled=true ./
```
Contributed by @ematipico
Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @ematipico
Add new options --write, --fix (alias of --write) and --unsafe to the command biome lint and biome check. Add a new option --fix (alias of --write) to the command biome format and biome migrate.
```
biome <lint|check> --<write|fix> [--unsafe]
biome format --<write|fix>
biome migrate --<write|fix>
```
The biome <lint|check> --<write|fix> has the same behavior as biome <lint|check> --apply. The biome <lint|check> --<write|fix> --unsafe has the same behavior as biome <lint|check> --apply-unsafe. The biome format --fix has the same behavior as biome format --write. The biome migrate --fix has the same behavior as biome migrate --write.

This change allows these commands to write modifications in the same options. With this change, the --apply and --apply-unsafe options are deprecated.

Contributed by @unvalley

Enhancements

Biome now executes commands (lint, format, check and ci) on the working directory by default. #2266 Contributed by @unvalley
```
- biome check .
+ biome check    # You can run the command without the path
```
biome migrate eslint now tries to convert ESLint ignore patterns into Biome ignore patterns.

ESLint uses gitignore patterns. Biome now tries to convert these patterns into Biome ignore patterns.

For example, the gitignore pattern /src is a relative path to the file in which it appears. Biome now recognizes this and translates this pattern to ./src.

Contributed by @Conaclos
biome migrate eslint now supports the eslintIgnore field in package.json.

ESLint allows the use of package.json as an ESLint configuration file. ESLint supports two fields: eslintConfig and eslintIgnore. Biome only supported the former. It now supports both.

Contributed by @Conaclos
biome migrate eslint now propagates NodeJS errors to the user.

This will help users to identify why Biome is unable to load some ESLint configurations.

Contributed by @Conaclos

Add a new --reporter called summary. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed. Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:

Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to be formatted:
main.ts
index.ts

Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to have their imports sorted:
main.ts
index.ts

Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Some analyzer rules were triggered

Rule Name                                               Diagnostics
lint/suspicious/noImplicitAnyLet                        12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDoubleEquals                          8 (8 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noRedeclare                             12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDebugger                              20 (20 error(s), 0 warning(s), 0 info(s))

Contributed by @ematipico

biome ci now enforces printing the output using colours. If you were previously using --colors=force, you can remove it because it's automatically set. Contributed by @ematipico

Add a new --reporter called github. This reporter will print diagnostics using GitHub workflow commands:

::error title=lint/suspicious/noDoubleEquals,file=main.ts,line=4,endLine=4,col=3,endColumn=5::Use === instead of ==
::error title=lint/suspicious/noDebugger,file=main.ts,line=6,endLine=6,col=1,endColumn=9::This is an unexpected use of the debugger statement.
::error title=lint/nursery/noEvolvingAny,file=main.ts,line=8,endLine=8,col=5,endColumn=6::This variable's type is not allowed to evolve implicitly, leading to potential any types.

Contributed by @ematipico

Add a new --reporter called junit. This reporter will print diagnostics using GitHub workflow commands:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Biome" tests="16" failures="16" errors="20" time="<TIME>">
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.suspicious.noDoubleEquals" line="4" column="3">
          <failure message="Use === instead of ==. == is only allowed when comparing against `null`">line 3, col 2, Use === instead of ==. == is only allowed when comparing against `null`</failure>
      </testcase>
  </testsuite>
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.suspicious.noDebugger" line="6" column="1">
          <failure message="This is an unexpected use of the debugger statement.">line 5, col 0, This is an unexpected use of the debugger statement.</failure>
      </testcase>
  </testsuite>
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.nursery.noEvolvingAny" line="8" column="5">
          <failure message="This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.">line 7, col 4, This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.</failure>
      </testcase>
  </testsuite>
</testsuites>

Contributed by @ematipico

Bug fixes

Fix #3024, where running biome init would create biome.json even if biome.jsonc already exists. Contributed by @minht11

Configuration

New features

Add an rule option fix to override the code fix kind of a rule (#2882).

A rule can provide a safe or an unsafe code action. You can now tune the kind of code actions thanks to the fix option. This rule option takes a value among:
- none: the rule no longer emits code actions.
- safe: the rule emits safe code action.
- unsafe: the rule emits unsafe code action.
The following configuration disables the code actions of noUnusedVariables, makes the emitted code actions of style/useConst and style/useTemplate unsafe and safe respectively.
```
{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        },
        "style": {
          "useConst": {
            "level": "warn",
            "fix": "unsafe"
          },
          "useTemplate": {
            "level": "warn",
            "fix": "safe"
          }
        }
      }
    }
  }
}
```
Contributed by @Conaclos
Add option javascript.linter.enabled to control the linter for JavaScript (and its super languages) files. Contributed by @ematipico
Add option json.linter.enabled to control the linter for JSON (and its super languages) files. Contributed by @ematipico
Add option css.linter.enabled to control the linter for CSS (and its super languages) files. Contributed by @ematipico
Add option css.formatter, to control the formatter options for CSS (and its super languages) files. Contributed by @ematipico
You can now change the severity of lint rules down to "info". The "info" severity doesn't emit error codes, and it isn't affected by other options like --error-on-warnings:
```
{
  "linter": {
    "rules": {
      "suspicious": {
        "noDebugger": "info"
      }
    }
  }
}
```
Contributed by @ematipico

Enhancements

The javascript.formatter.trailingComma option is deprecated and renamed to javascript.formatter.trailingCommas. The corresponding CLI option --trailing-comma is also deprecated and renamed to --trailing-commas. Details can be checked in #2492. Contributed by @Sec-ant

Bug fixes

Fix a bug where if the formatter was disabled at the language level, it could be erroneously enabled by an override that did not specify the formatter section #2924. Contributed by @dyc3
Fix #2990, now Biome doesn't add a trailing comma when formatting biome.json. Contributed by @dyc3

Editors

New features

Add support for LSP Workspaces

Enhancements

The LSP doesn't crash anymore when the configuration file contains errors. If the configuration contains errors, Biome now shows a pop-up to the user, and it will only parse files using the default configuration. Formatting and linting is disabled until the configuration file is fixed. Contributed by @ematipico

Bug fixes

Fixes #2781, by correctly computing the configuration to apply to a specific file. Contributed by @ematipico

Formatter

Bug fixes

Fix #2470 by avoid introducing linebreaks in single line string interpolations. Contributed by @ah-yu
Resolve deadlocks by narrowing the scope of locks. Contributed by @mechairoi
Fix #2782 by computing the enabled rules by taking the override settings into consideration. Contributed by @ematipico
Fix [https://github.com/biomejs/biome/issues/2877] by correctly handling line terminators in JSX string. Contributed by @ah-yu

Linter

Promoted rules

New rules are incubated in the nursery group. Once stable, we promote them to a stable group. The following rules are promoted:

New features

Add nursery/useDateNow. Contributed by @minht11
Add nursery/useErrorMessage. Contributed by @minht11
Add nursery/useThrowOnlyError. Contributed by @minht11
Add nursery/useImportExtensions. Contributed by @minht11

useNamingConvention now supports an option to enforce custom conventions (#1900).

For example, you can enforce the use of a prefix for private class members:

{
	"linter": {
		"rules": {
			"style": {
				"useNamingConvention": {
					"level": "error",
					"options": {
						"conventions": [
							{
								"selector": {
									"kind": "classMember",
									"modifiers": ["private"]
								},
								"match": "_(.*)",
                "formats": ["camelCase"]
							}
						]
					}
				}
			}
		}
	}
}

Please, find more details in the rule documentation.

Contributed by @Conaclos

Add nursery/useNumberToFixedDigitsArgument. Contributed by @minht11
Add nursery/useThrowNewError. Contributed by @minht11
Add nursery/useTopLevelRegex, which enforces defining regular expressions at the top level of a module. #2148 Contributed by @dyc3.
Add nursery/noCssEmptyBlock. #2513 Contributed by @togami2864
Add nursery/noDuplicateAtImportRules. #2658 Contributed by @DerTimonius
Add nursery/noDuplicateFontNames. #2308 Contributed by @togami2864
Add nursery/noDuplicateSelectorsKeyframeBlock. #2534 Contributed by @isnakode
Add nursery/noImportantInKeyframe. #2542 Contributed by @isnakode
Add nursery/noInvalidPositionAtImportRule. #2717 Contributed by @t-shiratori
Add nursery/noUnknownFunction. #2570 Contributed by @neokidev
Add nursery/noUnknownMediaFeatureName. #2751 Contributed by @Kazuhiro-Mimaki
Add nursery/noUnknownProperty. #2755 Contributed by @chansuke
Add nursery/noUnknownPseudoElement. #2655 Contributed by @keita-hino
Add nursery/noUnknownUnit. #2535 Contributed by @neokidev
Add nursery/noUnmatchableAnbSelector. #2706 Contributed by @togami2864
Add nursery/useGenericFontNames. #2573 Contributed by @togami2864
Add nursery/noYodaExpression. Contributed by @michellocana
Add nursery/noUnusedFunctionParameters Contributed by @printfn
Add nursery/UseSemanticElements. Contributed by @fujiyamaorange

Enhancements

Add a code action for noConfusingVoidType and improve the diagnostics.

The rule now suggests using undefined instead of void in confusing places. The diagnosis is also clearer.

Contributed by @Conaclos
Improve code action for nursery/noUselessUndefinedInitialization to handle comments.

The rule now places inline comments after the declaration statement, instead of removing them. The code action is now safe to apply.

Contributed by @lutaok
Make useExhaustiveDependencies report duplicate dependencies. Contributed by @tunamaguro
Rename noEvolvingAny into noEvolvingTypes (#48). Contributed by @Conaclos

Bug fixes

noUndeclaredVariables and noUnusedImports now correctly handle import namespaces (#2796).

Previously, Biome bound unqualified type to import namespaces. Import namespaces can only be used as qualified names in a type (ambient) context.

// Unused import
import * as Ns1 from "";
// This doesn't reference the import namespace `Ns1`
type T1 = Ns1; // Undeclared variable `Ns1`

// Unused import
import type * as Ns2 from "";
// This doesn't reference the import namespace `Ns2`
type T2 = Ns2; // Undeclared variable `Ns2`

import type * as Ns3 from "";
// This references the import namespace because it is a qualified name.
type T3 = Ns3.Inner;
// This also references the import namespace.
export type { Ns3 }

Contributed by @Conaclos

noUndeclaredVariables now correctly handle ambient computed member names (#2975).

A constant can be imported as a type and used in a computed member name of a member signature. Previously, Biome was unable to bind the value imported as a type to the computed member name.
```
import type { NAME } from "./constants.js";
type X = { [NAME]: number };
```
Contributed by @Conaclos
noUndeclaredVariables now ignores this in JSX components (#2636).

The rule no longer reports this as undeclared in following code.
```
import { Component } from 'react';

export class MyComponent extends Component {
  render() {
    return <this.foo />
  }
}
```
Contributed by @printfn and @Conaclos
useJsxKeyInIterable now handles more cases involving fragments. See the snippets below. Contributed by @dyc3

// valid
[].map((item) => {
	return <>{item.condition ? <div key={item.id} /> : <div key={item.id}>foo</div>}</>;
});

// invalid
[].map((item) => {
	return <>{item.condition ? <div /> : <div>foo</div>}</>;
});

noExcessiveNestedTestSuites no longer erroneously alerts on describe calls that are not invoking the global describe function. #2599 Contributed by @dyc3

// now valid
z.object({})
  .describe('')
  .describe('')
  .describe('')
  .describe('')
  .describe('')
  .describe('');

noEmptyBlockStatements no longer reports empty constructors using typescript parameter properties. #3005 Contributed by @dyc3
noEmptyBlockStatements no longer reports empty private or protected constructors. Contributed by @dyc3
noExportsInTest rule no longer treats files with in-source testing as test files https://github.com/biomejs/biome/issues/2859. Contributed by @ah-yu

useSortedClasses now keeps leading and trailing spaces when applying the code action inside template literals:

i Unsafe fix: Sort the classes.

  1 1 │   <>
  2   │ - → <div·class={`${variable}·px-2·foo·p-4·bar`}/>
    2 │ + → <div·class={`${variable}·foo·bar·p-4·px-2`}/>
  3 3 │   	<div class={`px-2 foo p-4 bar ${variable}`}/>
  4 4 │   </>

noUndeclaredDependencies is correctly triggered when running biome ci. Contributed by @ematipico
noUnusedVariables no longer panics when a certain combination of characters is typed. Contributed by @ematipico
noUndeclaredVariables no logger alerts on arguments object in a function scope. Contributed by @ah-yu

Parser

Enhancements

lang="tsx" is now supported in Vue Single File Components. #2765 Contributed by @dyc3

Bug fixes

The const modifier for type parameters is now accepted for TypeScript new signatures (#2825).

The following code is now correctly parsed:
```
interface I {
  new<const T>(x: T): T
}
```
Contributed by @Conaclos
Some invalid TypeScript syntax caused the Biome parser to crash.

The following invalid syntax no longer causes the Biome parser to crash:
```
declare using x: null;
declare qwait using x: null;
```
Contributed by @Conaclos

…

@biomejs/biome - npm Package Versions

1.9.1-nightly.12688b6

1.9.0

.css-1z04cui{margin-bottom:var(--chakra-space-4);font-size:var(--chakra-fontSizes-md);}v1.9.0 (2024-09-12)

Analyzer

CLI

New features

Enhancements

Bug fixes

Configuration

Editors

Formatter

Linter

Promoted rules

Deprecated rules

New features

Enhancements

Bug fixes

Parser

Enhancements

Bug fixes

1.8.4-nightly.7aaf0ce

1.8.4-nightly.d079e53

1.8.4-nightly.bd1d0c6

1.8.4-nightly.a579bf7

1.8.3

v1.8.3 (2024-06-27)

CLI

Bug fixes

Parser

Bug fixes

Formatter

Bug fixes

Linter

New features

Enhancements

Bug fixes

Enhancements

1.8.2

v1.8.2 (2024-06-20)

CLI

Bug fixes

Enhancement

Configuration

Bug fixes

Formatter

Bug fixes

JavaScript APIs

Bug fixes

Linter

New features

Enhancements

Bug fixes

Parser

Bug fixes

1.8.1

v1.8.1 (2024-06-10)

CLI

Bug fixes

Configuration

Bug fixes

Formatter

Bug fixes

Linter

New features

Bug fixes

Parser

Bug fixes

1.8.0

1.8.0 (2024-06-04)

Analyzer

New features

Enhancements

CLI

New features

Enhancements

Bug fixes

Configuration

New features

Enhancements

v1.9.0 (2024-09-12)