github biomejs/biome js-api/v0.6.0-nightly.af70ac2
JavaScript APIs v0.6.0-nightly.af70ac2
on GitHub

latest releases: cli/v1.9.5-nightly.c0cccb2, cli/v1.9.5-nightly.ff02a0b, cli/v1.9.5-nightly.4713c52...
pre-release6 months ago

Analyzer

Enhancements

  • Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @dyc3

CLI

New features

  • Add a new option --rule to the command biome lint (#58).

    This new option allows you to execute a single rule or a rule group.
    This option is convenient to test a rule or apply the code fixes of a single rule.

    For example, you can execute the style/useNamingConvention rule on the working directory: 

    biome lint --rule=style/useNamingConvention ./

    If the rule has a code action (autofix), you can use --apply to apply the fix: 

    biome lint --rule=style/useNamingConvention --apply ./

    The option takes the rule options in the Biome configuration file into account.
    Only, the severity level of the rule is overridden by its default value,
    i.e. error for a recommended rule or warn otherwise.

    You can also run a group of rules: 

    biome lint --rule=suspicious src/main.js

    In this case, the severity level of a rule is not overridden.
    Thus, the disabled rules stay disabled.
    To ensure that the group is run, the recommended field of the group is turned on.
    The nursery group cannot be passed because no rules are enabled in the nursery group by default.

    The option is compatible with other options such as --apply, --apply-unsafe 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

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

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

Editors

New features

  • Add support for LSP Workspaces

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

JavaScript APIs

Linter

New features

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

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 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('');

  • noExportsInTest rule no longer treats files with in-source testing as test files #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

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

What's Changed

Other changes

New Contributors

Full Changelog: cli/v1.7.3...js-api/v0.6.0-nightly.af70ac2

Check out latest releases or
releases around biomejs/biome js-api/v0.6.0-nightly.af70ac2

Don't miss a new biome release

NewReleases is sending notifications on new releases.

Get notifications