@biomejs/cli-darwin-arm64 - npm Package Versions

1.5.3 (2024-01-22)

LSP

Bug fixes

• Fix #1584. Ensure the LSP only registers the formatter once. Contributed by @nhedger

• Fix #1589. Fix invalid formatting of own line comments when they were at the end of an import/export list. Contributed by @spanishpear

Configuration

Bug fixes

• Override correctly the recommended preset (#1349).

  Previously, if unspecified, Biome turned on the recommended preset in overrides. This resulted in reporting diagnostics with a severity level set to off. This in turn caused Biome to fail.

  Now Biome won't switch on the recommended preset in overrides unless told to do so.

  Contributed by @Conaclos

• Don't format ignored files that are well-known JSONC files when files.ignoreUnknown is enabled (#1607).

  Previously, Biome always formatted files that are known to be JSONC files (e.g. .eslintrc) when files.ignoreUnknown was enabled.

  Contributed by @Conaclos

Formatter

New features

• Add option json.formatter.trailingCommas, to provide a better control over the trailing comma in JSON/JSONC files. Its default value is "none".

Bug fixes

• Fix #1178, where the line ending option wasn't correctly applied. Contributed by @ematipico
• Fix #1571. Fix invalid formatting of nested multiline comments. Contributed by @ah-yu

Linter

Bug fixes

Fix #1575. noArrayIndexKey now captures array index value inside template literals and with string concatination. Contributed by @vasucp1207

• Linter rules that inspect regexes now handle multibyte characters correctly (#1522).

  Previously, noMisleadingCharacterClass, noMultipleSpacesInRegularExpressionLiterals, and noEmptyCharacterClassInRegex made Biome errors on multi-bytes characters. Multibyte characters are now handled correctly.

  The following code no longer raises an internal error:

  // Cyrillic characters
  /[\u200E\u2066-\u2069]/gu;
  

  Contributed by @Conaclos

• useExhaustiveDependencies no longer made Biome errors in code TypeScript import equal declarations (#1194). Contributed by @Conaclos

• Fix typo in the diagnostic of noNodejsModules. Contributed by @huseeiin

Parser

Bug fixes

• Accept the const modifier for type parameter in method type signature (#1624).

  The following code is now correctly parsed:

  type Foo = {
    <const T>();
    method<const T>();
  };
  

  Contributed by @magic-akari

• Correctly parse type arguments in expression(#1184).

  The following code is now correctly parsed in typescript:

  0 < (0 >= 1);
  

  Contributed by @ah-yu

Website

New

• Add a page that maps the Biome rule to its source. Contributed by @ematipico

Fixes

• Generate Open Graph images based on the linked page. Contributed by @ematipico

• Fix examples of the git hook page. Contributed by @9renpoto, @lmauromb, and @Conaclos

• Fix dead and erroneous hyperlinks. Contributed by @Sec-ant and Conaclos

1.5.2 (2024-01-15)

CLI

Bug fixes

• Fix #1512 by skipping verbose diagnostics from the count. Contributed by @ematipico

• Correctly handle cascading include and ignore.

  Previously Biome incorrectly included files that were included at tool level and ignored at global level. In the following example, file.js was formatted when it should have been ignored. Now, Biome correctly ignores the directory ./src/sub/.

  ❯ tree src
    src
    └── sub
        └── file.js
  
  ❯ cat biome.json
    {
      "files": { "ignore": ["./src/sub/"] },
      "formatter": { "include": ["./src"] }
    }
  

  Contributed by @Conaclos

• Don't emit verbose warnings when a protected file is ignored.

  Some files, such as package.json and tsconfig.json, are protected. Biome emits a verbose warning when it encounters a protected file.

  Previously, Biome emitted this verbose warning even if the file was ignored by the configuration. Now, it doesn't emit verbose warnings for protected files that are ignored.

  Contributed by @Conaclos

• overrides no longer affect which files are ignored. Contributed by @Conaclos

• The file biome.json can't be ignored anymore. Contributed by @ematipico

• Fix #1541 where the content of protected files wasn't returned to stdout. Contributed by @ematipico

• Don't handle CSS files, the formatter isn't ready yet. Contributed by @ematipico

Configuration

Bug fixes

• Fix 1440, a case where extends and overrides weren't correctly emitting the final configuration. Contributed by @arendjr

• Correctly handle include when ignore is set (#1468). Contributed by @Conaclos

  Previously, Biome ignored include if ignore was set. Now, Biome check both include and ignore. A file is processed if it is included and not ignored. If include is not set all files are considered included.

Formatter

Bug fixes

• Fix placement of comments before * token in generator methods with decorators. #1537 Contributed by @ah-yu

• Fix #1406. Ensure comments before the async keyword are placed before it. Contributed by @ah-yu

• Fix #1172. Fix placement of line comment after function expression parentheses, they are now attached to first statement in body. Contributed by @kalleep

• Fix #1511 that made the JavaScript formatter crash. Contributed @Conaclos

Linter

Enhancements

• Add an unsafe code fix for noConsoleLog. Contributed by @vasucp1207

• useArrowFunction no longer reports function in extends clauses or in a new expression. Contributed by @Conaclos

  These cases require the presence of a prototype.

• Add dependency variable names on error message when useExhaustiveDependencies rule shows errors. Contributed by @mehm8128

Bug fixes

• The fix of useArrowFunction now adds parentheses around the arrow function in more cases where it is needed (#1524).

  A function expression doesn't need parentheses in most expressions where it can appear. This is not the case with the arrow function. We previously added parentheses when the function appears in a call or member expression. We now add parentheses in binary-like expressions and other cases where they are needed, hopefully covering all cases.

  Previously:

  - f = f ?? function() {};
  + f = f ?? () => {};
  

  Now:

  - f = f ?? function() {};
  + f = f ?? (() => {});
  

  Contributed by @Conaclos

• Fix #1514. Fix autofix suggestion to avoid the syntax error in no_useless_fragments. Contributed by @togami2864

1.5.1 (2024-01-10)

CLI

Bug fixes

• The diagnostics files/missingHandler are now shown only when the option --verbose is passed. Contributed by @ematipico
• The diagnostics for protected files are now shown only when the option --verbose is passed. Contributed by @ematipico
• Fix #1465, by taking in consideration the workspace folder when matching a pattern. Contributed by @ematipico
• Fix #1465, by correctly process globs that contain file names. Contributed by @ematipico

Formatter

Bug fixes

• Fix #1170. Fix placement of comments inside default switch clause. Now all line comments that have a preceding node will keep their position. Contributed by @kalleep

Linter

Bug fixes

Fix #1335. noUselessFragments now ignores code action on component props when the fragment is empty. Contributed by @vasucp1207

• useConsistentArrayType was accidentally placed in the style rule group instead of the nursery group. It is now correctly placed under nursery.

Fix #1483. useConsistentArrayType now correctly handles its option. Contributed by @Conaclos

Fix #1502. useArrowFunction now correctly handle functions that return a (comma) sequence expression. Contributed by @Conaclos

Previously the rule made an erroneous suggestion:

- f(function() { return 0, 1; }, "");
+ f(() => 0, 1, "")

Now, the rule wraps any comma sequence between parentheses:

- f(function() { return 0, 1; }, "");
+ f(() => (0, 1), "")

Fix #1473: useHookAtTopLevel now correctly handles React components and hooks that are nested inside other functions. Contributed by @arendjr