1.3.3 (2023-10-31)

Analyzer

Bug fixes

• Fix #604 which made noConfusingVoidType report false positives when the void type is used in a generic type parameter. Contributed by @unvalley

CLI

Bug fixes

• Fix how overrides behave. Now ignore and include apply or not the override pattern, so they override each other. Now the options inside overrides override the top-level options.
• Bootstrap the logger only when needed. Contributed by @ematipico
• Fix how overrides are run. The properties ignore and include have different semantics and only apply/not apply an override. Contributed by @ematipico

Editors

Bug fixes

• Fix #592, by changing binary resolution in the IntelliJ plugin. Contributed by @Joshuabaker2

Formatter

Bug fixes

• Apply the correct layout when the right hand of an assignment expression is an await expression or a yield expression. Contributed by @ematipico

• Fix #303, where nested arrow functions didn't break. Contributed by @victor-teles

Linter

New features

• Add noUnusedPrivateClassMembers rule. The rule disallow unused private class members. Contributed by @victor-teles

Bug fixes

• Fix #175 which made noRedeclare report index signatures using the name of a variable in the parent scope.

• Fix #557 which made noUnusedImports report imported types used in typeof expression. Contributed by @Conaclos

• Fix #576 by removing some erroneous logic in noSelfAssign. Contributed by @ematipico

• Fix #861 that made noUnusedVariables always reports the parameter of a non-parenthesize arrow function as unused.

• Fix #595 by updating unsafe-apply logic to avoid unexpected errors in noUselessFragments. Contributed by @nissy-dev

• Fix #591 which made noRedeclare report type parameters with identical names but in different method signatures. Contributed by @Conaclos

• Support more a11y roles and fix some methods for a11y lint rules Contributed @nissy-dev

• Fix #609 useExhaustiveDependencies, by removing useContext, useId and useSyncExternalStore from the known hooks. Contributed by @msdlisper

• Fix useExhaustiveDependencies, by removing useContext, useId and useSyncExternalStore from the known hooks. Contributed by @msdlisper

• Fix #871 and #610. Now useHookAtTopLevel correctly handles nested functions. Contributed by @arendjr

• The options of the rule useHookAtTopLevel are deprecated and will be removed in Biome 2.0. The rule now determines the hooks using the naming convention set by React.

  {
    "linter": {
      "rules": {
        "correctness": {
  +        "useHookAtTopLevel": "error",
  -        "useHookAtTopLevel": {
  -          "level": "error",
  -          "options": {
  -            "hooks": [
  -              {
  -                "name": "useLocation",
  -                "closureIndex": 0,
  -                "dependenciesIndex": 1
  -              },
  -              { "name": "useQuery", "closureIndex": 1, "dependenciesIndex": 0 }
  -            ]
  -          }
  -        }
        }
      }
    }
  }
  

Parser

Enhancements

• Support RegExp v flag. Contributed by @nissy-dev
• Improve error messages. Contributed by @ematipico

1.3.1 (2023-10-20)

CLI

Bug fixes

• Fix rage command, now it doesn't print info about running servers. Contributed by @ematipico

Editors

Bug fixes

• Fix #552, where the formatter isn't correctly triggered in Windows systems. Contributed by @victor-teles

Linter

New features

• Add noThisInStatic rule. Contributed by @ditorodev and @Conaclos

Bug fixes

• Fix #548 which made noSelfAssign panic.

• Fix #555, by correctly map globals into the workspace.

1.3.0 (2023-10-19)

Analyzer

Enhancements

• Import sorting is safe to apply now, and it will be applied when running check --apply instead of check --apply-unsafe.

• Import sorting now handles Bun imports bun:<name>, absolute path imports /<path>, and Node's subpath imports #<name>. See our documentation for more details. Contributed by @Conaclos

CLI

Bug fixes

• Fix #319. The command biome lint now shows the correct options. Contributed by @ematipico
• Fix #312. Running biome --version now exits with status code 0 instead of 1. Contributed by @nhedger
• Fix a bug where the extends functionality doesn't carry over organizeImports.ignore. Contributed by @ematipico
• The CLI now returns the original content when using stdin and the original content doesn't change. Contributed by @ematipico

New features

• Add support for BIOME_BINARY environment variable to override the location of the binary. Contributed by @ematipico

• Add option --indent-width, and deprecated the option --indent-size. Contributed by @ematipico

• Add option --javascript-formatter-indent-width, and deprecated the option --javascript-formatter-indent-size. Contributed by @ematipico

• Add option --json-formatter-indent-width, and deprecated the option --json-formatter-indent-size. Contributed by @ematipico

• Add option --daemon-logs to biome rage. The option is required to view Biome daemon server logs. Contributed by @unvalley

• Add support for logging. By default, Biome doesn't log anything other than diagnostics. Logging can be enabled with the new option --log-level:

  biome format --log-level=info ./src
  

  There are four different levels of logging, from the most verbose to the least verbose: debug, info, warn and error. Here's how an INFO log will look like:

  2023-10-05T08:27:01.954727Z  INFO  Analyze file ./website/src/playground/components/Resizable.tsx
    at crates/biome_service/src/file_handlers/javascript.rs:298 on biome::worker_5
    in Pulling diagnostics with categories: RuleCategories(SYNTAX)
    in Processes formatting with path: "./website/src/playground/components/Resizable.tsx"
    in Process check with path: "./website/src/playground/components/Resizable.tsx"
  

  You can customize how the log will look like with a new option --log-kind. The supported kinds are: pretty, compact and json.

  pretty is the default logging. Here's how a compact log will look like:

  2023-10-05T08:29:04.864247Z  INFO biome::worker_2 Process check:Processes linting:Pulling diagnostics: crates/biome_service/src/file_handlers/javascript.rs: Analyze file ./website/src/playground/components/Resizable.tsx path="./website/src/playground/components/Resizable.tsx" path="./website/src/playground/components/Resizable.tsx" categories=RuleCategories(LINT)
  2023-10-05T08:29:04.864290Z  INFO biome::worker_7 Process check:Processes formatting: crates/biome_service/src/file_handlers/javascript.rs: Format file ./website/src/playground/components/Tabs.tsx path="./website/src/playground/components/Tabs.tsx" path="./website/src/playground/components/Tabs.tsx"
  2023-10-05T08:29:04.879332Z  INFO biome::worker_2 Process check:Processes formatting:Pulling diagnostics: crates/biome_service/src/file_handlers/javascript.rs: Analyze file ./website/src/playground/components/Resizable.tsx path="./website/src/playground/components/Resizable.tsx" path="./website/src/playground/components/Resizable.tsx" categories=RuleCategories(SYNTAX)
  2023-10-05T08:29:04.879383Z  INFO biome::worker_2 Process check:Processes formatting: crates/biome_service/src/file_handlers/javascript.rs: Format file ./website/src/playground/components/Resizable.tsx path="./website/src/playground/components/Resizable.tsx" path="./website/src/playground/components/Resizable.tsx"
  

Enhancements

• Deprecated the environment variable ROME_BINARY. Use BIOME_BINARY instead. Contributed by @ematipico
• Biome doesn't check anymore the presence of the .git folder when VCS support is enabled. Contributed by @ematipico
• biome rage doesn't print the logs of the daemon, use biome rage --daemon-logs to print them. Contributed by @unvalley

Configuration

New features

• Add option formatter.indentWidth, and deprecated the option formatter.indentSize. Contributed by @ematipico

• Add option javascript.formatter.indentWidth, and deprecated the option javascript.formatter.indentSize. Contributed by @ematipico

• Add option json.formatter.indentWidth, and deprecated the option json.formatter.indentSize. Contributed by @ematipico

• Add option include to multiple sections of the configuration

  • files.include;
  • formatter.include;
  • linter.include;
  • organizeImports.include; When include and ignore are both specified, ignore takes precedence over include

• Add option overrides, where users can modify the behaviour of the tools for certain files or paths.

  For example, it's possible to modify the formatter lineWidth, and even quoteStyle for certain files that are included in glob path generated/**:

  {
    "formatter": {
      "lineWidth": 100
    },
    "overrides": [
      {
        "include": ["generated/**"],
        "formatter": {
          "lineWidth": 160
        },
        "javascript": {
          "formatter": {
            "quoteStyle": "single"
          }
        }
      }
    ]
  }
  

  Or, you can disable certain rules for certain path, and disable the linter for other paths:

  {
    "linter": {
      "enabled": true,
      "rules": {
        "recommended": true
      }
    },
    "overrides": [
      {
        "include": ["lib/**"],
        "linter": {
          "rules": {
            "suspicious": {
              "noDebugger": "off"
            }
          }
        }
      },
      {
        "include": ["shims/**"],
        "linter": {
          "enabled": false
        }
      }
    ]
  }
  

Bug fixes

• Fix #343, extends was incorrectly applied to the biome.json file. Contributed by @ematipico

Editors

Bug fixes

• Fix #404. Biome intellij plugin now works on Windows. Contributed by @victor-teles

• Fix #402. Biome format on intellij plugin now recognize biome.json. Contributed by @victor-teles

Formatter

Enhancements

• Use OnceCell for the Memoized memory because that's what the RefCell<Option> implemented. Contributed by @denbezrukov

Linter

Promoted rules

• complexity/noExcessiveCognitiveComplexity
• complexity/noVoid
• correctness/useExhaustiveDependencies
• correctness/useHookAtTopLevel
• performance/noAccumulatingSpread
• style/useCollapsedElseIf
• suspicious/noConfusingVoidType
• suspicious/noFallthroughSwitchClause
• suspicious/noGlobalIsFinite
• suspicious/noGlobalIsNan
• suspicious/useIsArray

The following rules are now recommended:

• noAccumulatingSpread
• noConfusingVoidType
• noFallthroughSwitchClause
• noForEach

New features

• Add noEmptyCharacterClassInRegex rule. The rule reports empty character classes and empty negated character classes in regular expression literals. Contributed by @Conaclos

• Add noMisleadingInstantiator rule. The rule reports the misleading use of the new and constructor methods. Contributed by @unvalley

• Add noUselessElse rule. The rule reports else clauses that can be omitted because their if branches break. Contributed by @Conaclos

• Add noUnusedImports rule. The rule reports unused imports and suggests removing them. Contributed by @Conaclos

  noUnusedVariables reports also unused imports, but don't suggest their removal. Once noUnusedImports stabilized, noUnusedVariables will not report unused imports.

• Add useShorthandAssign rule. The rule enforce use of shorthand operators that combine variable assignment and some simple mathematical operations. For example, x = x + 4 can be shortened to x += 4. Contributed by @victor-teles

• Add useAsConstAssertion rule. The rule enforce use of as const assertion to infer literal types. Contributed by @unvalley

• Add noMisrefactoredShorthandAssign rule. The rule reports shorthand assigns when variable appears on both sides. For example x += x + b Contributed by @victor-teles

• Add noApproximativeNumericConstant rule. Contributed by @nikeee

Add noInteractiveElementToNoninteractiveRole rule. The rule enforces the non-interactive ARIA roles are not assigned to interactive HTML elements. Contributed by @nissy-dev

• Add useAriaActivedescendantWithTabindex rule. The rule enforces that tabIndex is assigned to non-interactive HTML elements with aria-activedescendant. Contributed by @nissy-dev

• Add noUselessLoneBlockStatements rule. The rule reports standalone blocks that don't include any lexical scoped declaration. Contributed by @emab

• Add noInvalidNewBuiltin rule. The rule reports use of new on Symbol and BigInt. Contributed by @lucasweng

Enhancements

• The following rules have now safe code fixes:

  • noNegationElse
  • noUselessLabel
  • noUselessTypeConstraint
  • noUnusedLabels
  • useConst
  • useEnumInitializers
  • useWhile

• noAccumulatingSpread makes more check in order to reduce potential false positives. Contributed by @Vivalldi

• noConstAssign now provides an unsafe code fix that replaces const with let. Contributed by @vasucp1207

• noExcessiveComplexity default complexity threshold is now 15. Contributed by @arendjr

• noPositiveTabindexValue now provides an unsafe code fix that set to 0 the tab index. Contributed by @vasucp1207

• noUnusedLabels no longer reports unbreakable labeled statements. Contributed by @Conaclos

• noUnusedVariables now reports unused TypeScript's type parameters. Contributed by @Conaclos

• useAnchorContent now provides an unsafe code fix that removes the `aria-hidden`` attribute. Contributed by @vasucp1207

• useValidAriaProps now provides an unsafe code fix that removes invalid properties. Contributed by @vasucp1207

• noExcessiveComplexity was renamed to noExcessiveCognitiveComplexity

Bug fixes

Fix #294. noConfusingVoidType no longer reports false positives for return types. Contributed by @b4s36t4

Fix #313. noRedundantUseStrict now keeps leading comments.

Fix #383. noMultipleSpacesInRegularExpressionLiterals now provides correct code fixes when consecutive spaces are followed by a quantifier. Contributed by @Conaclos

Fix #397. useNumericLiterals now provides correct code fixes for signed numbers. Contributed by @Conaclos

• Fix 452. The linter panicked when it met a malformed regex (a regex not ending with a slash).

• Fix #104. We now correctly handle types and values with the same name.

• Fix #243 a false positive case where the incorrect scope was defined for the infer type in rule noUndeclaredVariables. Contributed by @denbezrukov

• Fix #322, now noSelfAssign correctly handles literals inside call expressions.

• Changed how noSelfAssign behaves. The rule is not triggered anymore on function calls. Contributed by @ematipico

Parser

• Enhance diagnostic for infer type handling in the parser. The 'infer' keyword can only be utilized within the ' extends' clause of a conditional type. Using it outside this context will result in an error. Ensure that any type declarations using 'infer' are correctly placed within the conditional type structure to avoid parsing issues. Contributed by @denbezrukov

• Add support for parsing trailing commas inside JSON files:

  {
    "json": {
      "parser": {
        "allowTrailingCommas": true
      }
    }
  }
  

  Contributed by @nissy-dev

VSCode

1.2.2 (2023-09-16)

CLI

Bug fixes

• Fix a condition where import sorting wasn't applied when running biome check --apply

1.2.1 (2023-09-15)

Configuration

• Fix an edge case where the formatter language configuration wasn't picked.
• Fix the configuration schema, where json.formatter properties weren't transformed in camel case.

1.2.0 (2023-09-15)

CLI

New features

• Add new options to customize the behaviour the formatter based on the language of the file
  • --json-formatter-enabled
  • --json-formatter-indent-style
  • --json-formatter-indent-size
  • --json-formatter-line-width
  • --javascript-formatter-enabled
  • --javascript-formatter-indent-style
  • --javascript-formatter-indent-size
  • --javascript-formatter-line-width

Bug fixes

• Fix a bug where --errors-on-warning didn't work when running biome ci command.

Configuration

New features

• Add new options to customize the behaviour of the formatter based on the language of the file
  • json.formatter.enabled
  • json.formatter.indentStyle
  • json.formatter.indentSize
  • json.formatter.lineWidth
  • javascript.formatter.enabled
  • javascript.formatter.indentStyle
  • javascript.formatter.indentSize
  • javascript.formatter.lineWidth

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:

• a11y/noAriaUnsupportedElements
• a11y/noNoninteractiveTabindex
• a11y/noRedundantRoles
• a11y/useValidAriaValues
• complexity/noBannedTypes
• complexity/noStaticOnlyClass
• complexity/noUselessEmptyExport
• complexity/noUselessThisAlias
• correctness/noConstantCondition
• correctness/noNonoctalDecimalEscape
• correctness/noSelfAssign
• style/useLiteralEnumMembers
• style/useNamingConvention
• suspicious/noControlCharactersInRegex
• suspicious/noUnsafeDeclarationMerging
• suspicious/useGetterReturn

New rules

• Add noConfusingVoidType rule. The rule reports the unusual use of the void type. Contributed by @shulandmimi

Removed rules

• Remove noConfusingArrow

  Code formatters, such as prettier and Biome, always adds parentheses around the parameter or the body of an arrow function. This makes the rule useless.

  Contributed by @Conaclos

Enhancements

• noFallthroughSwitchClause now relies on control flow analysis to report most of the switch clause fallthrough. Contributed by @Conaclos

• noAssignInExpressions no longer suggest code fixes. Most of the time the suggestion didn't match users' expectations. Contributed by @Conaclos

• noUselessConstructor no longer emits safe code fixes. Contributed by @Conaclos

  All code fixes are now emitted as unsafe code fixes. Removing a constructor can change the behavior of a program.

• useCollapsedElseIf now only provides safe code fixes. Contributed by @Conaclos

• noUnusedVariables now reports more cases.

  The rule is now able to ignore self-writes. For example, the rule reports the following unused variable:

  let a = 0;
  a++;
  a += 1;
  

  The rule is also capable of detecting an unused declaration that uses itself. For example, the rule reports the following unused interface:

  interface I {
    instance(): I
  }
  

  Finally, the rule now ignores all TypeScript declaration files, including global declaration files.

  Contributed by @Conaclos

Bug fixes

• Fix #182, making useLiteralKeys retains optional chaining. Contributed by @denbezrukov

• Fix #168, fix useExhaustiveDependencies false positive case when stable hook is on a new line. Contributed by @denbezrukov

• Fix #137, fix noRedeclare false positive case with TypeScript module declaration:

  declare module '*.gif' {
      const src: string;
  }
  
  declare module '*.bmp' {
      const src: string;
  }
  

  Contributed by @denbezrukov

• Fix #258, fix noUselessFragments the case where the rule removing an assignment. Contributed by @denbezrukov

• Fix #266, where complexity/useLiteralKeys emitted a code action with an invalid AST. Contributed by @ematipico

• Fix #105, removing false positives reported by noUnusedVariables.

  The rule no longer reports the following used variable:

  const a = f(() => a);
  

  Contributed by @Conaclos

VSCode

Enhancements

• Improve server binary resolution when using certain package managers, notably pnpm.

  The new strategy is to point to node_modules/.bin/biome path, which is consistent for all package managers.