chore(deps): update dependency @biomejs/biome to v1.7.3

Open renovate[bot] opened this issue 2 years ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	`1.3.3` -> `1.7.3`

Release Notes

biomejs/biome (@biomejs/biome)

`v1.7.3`

Compare Source

CLI

Bug fixes

The stdin-file-path option now works correctly for Astro/Svelte/Vue files (#2686)

Fix #2225 where lint output become empty for Vue files.

Contributed by @tasshi-me
biome migrate eslint now correctly resolve @scope/eslint-config (#2705). Contributed by @Conaclos

Formatter

Linter

New features

Add nursery/useExplicitLengthCheck.

Bug fixes

noBlankTarget no longer hangs when applying a code fix (#2675).

Previously, the following code made Biome hangs when applying a code fix.
```
<a href="https://example.com" rel="" target="_blank"></a>
```
Contributed by @Conaclos
noRedeclare no longer panics on conditional type (#2659).

This is a regression introduced by #2394. This regression makes noRedeclare panics on every conditional types with infer bindings.

Contributed by @Conaclos
noUnusedLabels and noConfusingLabels now ignore svelte reactive statements (#2571).

The rules now ignore reactive Svelte blocks in Svelte components.
```
<script>
$: { /* reactive block */ }
</script>
```
Contributed by @Conaclos
useExportType no longer removes leading comments (#2685).

Previously, useExportType removed leading comments when it factorized the type qualifier. It now provides a code fix that preserves the leading comments:
```
- export {
+ export type {
    /**leading comment*/
-   type T
+   T
  }
```
Contributed by @Conaclos
useJsxKeyInIterable no longer reports false positive when iterating on non-jsx items (#2590).

The following snipet of code no longer triggers the rule:
```
<>{data.reduce((total, next) => total + next, 0)}</>
```
Contributed by @dyc3
Fix typo by renaming useConsistentBuiltinInstatiation to useConsistentBuiltinInstantiation Contributed by @minht11

`v1.7.2`

Compare Source

Analyzer

Bug fixes

Import sorting now ignores side effect imports (#817).

A side effect import consists now in its own group. This ensures that side effect imports are not reordered.

Here is an example of how imports are now sorted:
```
  import "z"
- import { D } from "d";
  import { C } from "c";
+ import { D } from "d";
  import "y"
  import "x"
- import { B } from "b";
  import { A } from "a";
+ import { B } from "b";
  import "w"
```
Contributed by @Conaclos
Import sorting now adds spaces where needed (#1665) Contributed by @Conaclos

CLI

Bug fixes

biome migrate eslint now handles cyclic references.

Some plugins and configurations export objects with cyclic references. This causes biome migrate eslint to fail or ignore them. These edge cases are now handled correctly.

Contributed by @Conaclos

Formatter

Bug fixes

Correctly handle placement of comments inside named import clauses. #2566. Contributed by @ah-yu

Linter

New features

Add nursery/noReactSpecificProps. Contributed by @marvin-j97
Add noUselessUndefinedInitialization. Contributed by @lutaok
Add nursery/useArrayLiterals. Contributed by @Kazuhiro-Mimaki
Add nursery/useConsistentBuiltinInstatiation. Contributed by @minht11
Add nursery/useDefaultSwitchClause. Contributed by @michellocana

Bug fixes

noDuplicateJsonKeys no longer crashes when a JSON file contains an unterminated string (#2357). Contributed by @Conaclos
noRedeclare now reports redeclarations of parameters in a functions body (#2394).

The rule was unable to detect redeclarations of a parameter or a type parameter in the function body. The following two redeclarations are now reported:
```
function f<T>(a) {
  type T = number; // redeclaration
  const a = 0; // redeclaration
}
```
Contributed by @Conaclos
noRedeclare no longer reports overloads in object types (#2608).

The rule no longer report redeclarations in the following code:
```
type Overloads = {
  ({ a }: { a: number }): number,
  ({ a }: { a: string }): string,
};
```
Contributed by @Conaclos
noRedeclare now merge default function export declarations and types (#2372).

The following code is no longer reported as a redeclaration:
```
interface Foo {}
export default function Foo() {}
```
Contributed by @Conaclos
noUndeclaredVariables no longer reports variable-only and type-only exports (#2637). Contributed by @Conaclos
noUnusedVariables no longer crash Biome when encountering a malformed conditional type (#1695). Contributed by @Conaclos
useConst now ignores a variable that is read before its assignment.

Previously, the rule reported the following example:
```
let x;
x; // read
x = 0; // write
```
It is now correctly ignored.

Contributed by @Conaclos
useShorthandFunctionType now suggests correct code fixes when parentheses are required (#2595).

Previously, the rule didn't add parentheses when they were needed. It now adds parentheses when the function signature is inside an array, a union, or an intersection.
```
- type Union = { (): number } | string;
+ type Union = (() => number) | string;
```
Contributed by @Conaclos
useTemplate now correctly escapes strings (#2580).

Previously, the rule didn't correctly escape characters preceded by an escaped character.

Contributed by @Conaclos
noMisplacedAssertion now allow these matchers
- expect.any()
- expect.anything()
- expect.closeTo
- expect.arrayContaining
- expect.objectContaining
- expect.stringContaining
- expect.stringMatching
- expect.extend
- expect.addEqualityTesters
- expect.addSnapshotSerializer
Contributed by @fujiyamaorange

Parser

Bug fixes

The language parsers no longer panic on unterminated strings followed by a newline and a space (#2606, #2410).

The following example is now parsed without making Biome panics:
```
"
 "
```
Contributed by @Conaclos

`v1.7.1`

Compare Source

Editors

Bug fixes

Fix #2403 by printing the errors in the client console. Contributed by @ematipico

Formatter

Bug fixes

Add parentheses for the return expression that has leading multiline comments. #2504. Contributed by @ah-yu
Correctly format dangling comments of continue statements. #2555. Contributed by @ah-yu

Linter

Bug fixes

Fix case where jsxRuntime wasn't being respected by useImportType rule (#2473).Contributed by @arendjr
Fix #2460, where the rule noUselessFragments was crashing the linter in some cases. Now cases like these are correctly handled:
```
callFunction(<>{bar}</>)
```
Contributed by @ematipico
Fix #2366, where noDuplicateJsonKeys incorrectly computed the kes to highlight. Contributed by @ematipico

Enhancements

The rule noMisplacedAssertions now considers valid calling expect inside waitFor:

import { waitFor } from '@&#8203;testing-library/react';

await waitFor(() => {
  expect(111).toBe(222);
});

Contributed by @ematipico

`v1.7.0`

Compare Source

Analyzer

Bug fixes

Now Biome can detect the script language in Svelte and Vue script blocks more reliably (#2245). Contributed by @Sec-ant
useExhaustiveDependencies no longer reports recursive calls as missing dependencies (#2361). Contributed by @arendjr
useExhaustiveDependencies correctly reports missing dependencies declared using function declarations (#2362). Contributed by @arendjr
Biome now can handle .svelte and .vue files with CRLF as the end-of-line sequence. Contributed by @Sec-ant
noMisplacedAssertion no longer reports method calls by describe, test, it objects (e.g. test.each([])()) (#2443). Contributed by @unvalley.
Biome now can handle .vue files with generic components (#2456).
```
<script generic="T extends Record<string, any>" lang="ts" setup>
//...
</script>
```
Contributed by @Sec-ant

Enhancements

Complete the well-known file lists for JSON-like files. Trailing commas are allowed in .jsonc files by default. Some well-known files like tsconfig.json and .babelrc don't use the .jsonc extension but still allow comments and trailing commas. While others, such as .eslintrc.json, only allow comments. Biome is able to identify these files and adjusts the json.parser.allowTrailingCommas option accordingly to ensure they are correctly parsed. Contributed by @Sec-ant
Fix dedent logic inconsistent with prettier where the indent-style is space and the indent-width is not 2. Contributed by @mdm317

CLI

New features

Add a command to migrate from ESLint

biome migrate eslint allows you to migrate an ESLint configuration to Biome. The command supports legacy ESLint configurations and new flat ESLint configurations. Legacy ESLint configurations using the YAML format are not supported.

When loading a legacy ESLint configuration, Biome resolves the extends field. It resolves both shared configurations and plugin presets! To do this, it invokes Node.js.

Biome relies on the metadata of its rules to determine the equivalent rule of an ESLint rule. A Biome rule is either inspired or roughly identical to an ESLint rules. By default, inspired and nursery rules are excluded from the migration. You can use the CLI flags --include-inspired and --include-nursery to migrate them as well.

Note that this is a best-effort approach. You are not guaranteed to get the same behavior as ESLint.

Given the following ESLint configuration:
```
{
      "ignore_patterns": ["**/*.test.js"],
      "globals": { "var2": "readonly" },
      "rules": {
          "eqeqeq": "error"
      },
      "overrides": [{
          "files": ["lib/*.js"],
          "rules": {
            "default-param-last": "off"
          }
      }]
}
```
biome migrate eslint --write changes the Biome configuration as follows:
```
{
  "linter": {
    "rules": {
      "recommended": false,
      "suspicious": {
        "noDoubleEquals": "error"
      }
    }
  },
  "javascript": { "globals": ["var2"] },
  "overrides": [{
    "include": ["lib/*.js"],
    "linter": {
      "rules": {
        "style": {
          "useDefaultParameterLast": "off"
        }
      }
    }
  }]
}
```
Also, if the working directory contains .eslintignore, then Biome migrates the glob patterns. Nested .eslintignore in subdirectories and negated glob patterns are not supported.

If you find any issue, please don't hesitate to report them.

Contributed by @Conaclos
Added two new options to customise the emitted output of the CLI: --reporter=json and --reporter=json-pretty. With --reporter=json, the diagnostics and the summary will be printed in the terminal in JSON format. With --reporter=json-pretty, you can print the same information, but formatted using the same options of your configuration.

NOTE: the shape of the JSON is considered experimental, and the shape of the JSON might change in the future.

Example of output when running `biome format` command
```json { "summary": { "changed": 0, "unchanged": 1, "errors": 1, "warnings": 0, "skipped": 0, "suggestedFixesSkipped": 0, "diagnosticsNotPrinted": 0 }, "diagnostics": [ { "category": "format", "severity": "error", "description": "Formatter would have printed the following content:", "message": [ { "elements": [], "content": "Formatter would have printed the following content:" } ], "advices": { "advices": [ { "diff": { "dictionary": " statement();\n", "ops": [ { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "equal": { "range": [2, 12] } } }, { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "equal": { "range": [12, 13] } } }, { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "insert": { "range": [13, 15] } } } ] } } ] }, "verboseAdvices": { "advices": [] }, "location": { "path": { "file": "format.js" }, "span": null, "sourceCode": null }, "tags": [], "source": null } ], "command": "format" } ```
Added new --staged flag to the check, format and lint subcommands.

This new option allows users to apply the command only to the files that are staged (the ones that will be committed), which can be very useful to simplify writing git hook scripts such as pre-commit. Contributed by @castarco

Enhancements

Improve support of .prettierignore when migrating from Prettier

Now, Biome translates most of the glob patterns in .prettierignore to the equivalent Biome ignore pattern. Only negated glob patterns are not supported.

Contributed by @Conaclos
Support JavaScript configuration files when migrating from Prettier

biome migrate prettier is now able to migrate Prettier configuration files ending with js, mjs, or cjs extensions. To do this, Biome invokes Node.js.

Also, embedded Prettier configurations in package.json are now supported.

Contributed by @Conaclos
Support overrides field in Prettier configuration files when migrating from Prettier. Contributed by @Conaclos
Support passing a file path to the --config-path flag or the BIOME_CONFIG_PATH environment variable.

Now you can pass a .json/.jsonc file path with any filename to the --config-path flag or the BIOME_CONFIG_PATH environment variable. This will disable the configuration auto-resolution and Biome will try to read the configuration from the said file path (#2265).
```
biome format --config-path=../biome.json ./src
```
Contributed by @Sec-ant

Bug fixes

Biome now tags the diagnostics emitted by organizeImports and formatter with correct severity levels, so they will be properly filtered by the flag --diagnostic-level (#2288). Contributed by @Sec-ant
Biome now correctly filters out files that are not present in the current directory when using the --changed flag #1996. Contributed by @castarco
Biome now skips traversing fifo or socket files (#2311). Contributed by @Sec-ant
Biome now resolves configuration files exported from external libraries in extends from the working directory (CLI) or project root (LSP). This is the documented behavior and previous resolution behavior is considered as a bug (#2231). Contributed by @Sec-ant

Configuration

Bug fixes

Now setting group level all to false can disable recommended rules from that group when top level recommended is true or unset. Contributed by @Sec-ant
Biome configuration files can correctly extends .jsonc configuration files now (#2279). Contributed by @Sec-ant
Fixed the JSON schema for React hooks configuration (#2396). Contributed by @arendjr

Enhancements

Biome now displays the location of a parsing error for its configuration file (#1627).

Previously, when Biome encountered a parsing error in its configuration file, it didn't indicate the location of the error. It now displays the name of the configuration file and the range where the error occurred.

Contributed by @Conaclos
options is no longer required for rules without any options (#2313).

Previously, the JSON schema required to set options to null when an object is used to set the diagnostic level of a rule without any option. However, if options is set to null, Biome emits an error.

The schema is now fixed and it no longer requires specifying options. This makes the following configuration valid:
```
{
  "linter": {
    "rules": {
      "style": {
        "noDefaultExport": {
          "level": "off"
        }
      }
    }
  }
}
```
Contributed by @Conaclos

Editors

Bug fixes

Biome extension is now able to parse the JSX syntax in files that associated with the javascript language identifier. This is an ad hoc fix, because in the React world, .js files are allowed to include JSX syntax, and these files are often associated with the javascript language identifier in most of the editors. Plus, some editor extensions will also associate .jsx files with the javascript language identifier. Relative links: discussion, #2085. Contributed by @Sec-ant

Formatter

Bug fixes

Fix #2291 by correctly handle comment placement for JSX spread attributes and JSX spread children. Contributed by @ah-yu

JavaScript APIs

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 a new option jsxRuntime to the javascript configuration. When set to reactClassic, the noUnusedImports and useImportType rules use this information to make exceptions for the React global that is required by the React Classic JSX transform.

This is only necessary for React users who haven't upgraded to the new JSX transform.

Contributed by @Conaclos and @arendjr
Implement #2043: The React rule useExhaustiveDependencies is now also compatible with Preact hooks imported from preact/hooks or preact/compat. Contributed by @arendjr
Add rule noFlatMapIdentity to disallow unnecessary callback use on flatMap. Contributed by @isnakode
Add rule noConstantMathMinMaxClamp, which disallows using Math.min and Math.max to clamp a value where the result itself is constant. Contributed by @mgomulak

Enhancements

style/useFilenamingConvention now allows prefixing a filename with + (#2341).

This is a convention used by Sveltekit and Vike.

Contributed by @Conaclos
style/useNamingConvention now accepts PascalCase for local and top-level variables.

This allows supporting local variables that hold a component or a regular class. The following code is now accepted:
```
function loadComponent() {
  const Component = getComponent();
  return <Component />;
}
```
Contributed by @Conaclos
complexity/useLiteralKeys no longer report computed properties named __proto__ (#2430).

In JavaScript, {["__proto__"]: null} and {__proto__: null} have not the same semantic. The first code set a regular property to null. The second one set the prototype of the object to null. See the MDN Docs for more details.

The rule now ignores computed properties named __proto__.

Contributed by @Conaclos

Bug fixes

Lint rules useNodejsImportProtocol, useNodeAssertStrict, noRestrictedImports, noNodejsModules will no longer check declare module statements anymore. Contributed by @Sec-ant
style/useNamingConvention now accepts any case for variables from object destructuring (#2332).

The following name is now ignored:
```
const { Strange_Style } = obj;
```
Previously, the rule renamed this variable. This led to a runtime error.

Contributed by @Conaclos

Parser

Bug fixes

Fixed an issue when Unicode surrogate pairs were encoded in JavaScript strings using an escape sequence (#2384). Contributed by @arendjr

`v1.6.4`

Compare Source

Analyzer

Bug fixes

An operator with no spaces around in a binary expression no longer breaks the js analyzer (#2243). Contributed by @Sec-ant

CLI

Bug fixes

Fix the printed error count (#2048). Contributed by @Sec-ant

Configuration

Bug fixes

Correctly calculate enabled rules in lint rule groups. Now a specific rule belonging to a group can be enabled even if its group-level preset option recommended or all is false (#2191). Contributed by @Sec-ant

Editors

Bug fixes

Fix the unexpected code deletion and repetition when quickfix.biome is enabled and some import-related rules are applied (#2222, #688, #1015). Contributed by @Sec-ant

Linter

Bug fixes

Fix #2211. noChildrenProp should work fine when children pass as a prop in a new line. Contributed by @fireairforce
Fix #2248. lint/a11y/useButtonType should not trigger when button element with spread attribute. Contributed by @fireairforce
Fix #2216. lint/style/useNamingConvention should not ignore JSX Component name binding. Contributed by @fireairforce

Enhancements

Add support for object property members in the rule useSortedClasses. Contributed by @ematipico

Parser

The parser doesn't throw any error when the frontmatter of .astro files contains an illegal return:

`v1.6.3`

Compare Source

Analyzer

CLI

Bug fixes

Fix configuration resolution. Biome is now able to correctly find the biome.jsonc configuration file when --config-path is explicitly set (#2164). Contributed by @Sec-ant
JavaScript/TypeScript files of different variants (.ts, .js, .tsx, .jsx) in a single workspace now have stable formatting behaviors when running the CLI command in paths of different nested levels or in different operating systems (#2080, #2109). Contributed by @Sec-ant

Configuration

Bug fixes

Complete the documentation and overrides support for options formatter.lineEnding, [language].formatter.lineEnding, formatter.attributePosition and javascript.formatter.attributePosition. Contributed by @Sec-ant

Editors

Formatter

Bug fixes

Fix #2172 by breaking long object destructuring patterns. Contributed by @ah-yu

JavaScript APIs

Linter

New features

Add rule noEvolvingAny to disallow variables from evolving into any type through reassignments. Contributed by @fujiyamaorange

Enhancements

Rename noSemicolonInJsx to noSuspiciousSemicolonInJsx. Contributed by @fujiyamaorange

LSP

Bug fixes

Quickfix action no longer autofixes lint rule errors on save when linter is disabled (#2161). Contributed by @Sec-ant
Range formatting for Astro/Svelte/Vue doesn't place code out of place, especially when formatting on paste is enabled. Contributed by @ematipico

Parser

`v1.6.2`

Compare Source

Analyzer

Bug fixes

The noSuperWithoutExtends rule now allows for calling super() in derived class constructors of class expressions (#2108). Contributed by @Sec-ant
Fix discrepancies on file source detection. Allow module syntax in .cts files (#2114). Contributed by @Sec-ant

CLI

Bug fixes

Fixes #2131, where folders were incorrectly ignored when running the command check. Now folders are correctly ignored based on their command. Contributed by @ematipico
Smoother handling of "endOfLine": "auto" in prettier migration: falling back to "lf" (#2145). Contributed by @eMerzh

Configuration

Bug fixes

Fix enabled rules calculation. The precendence of individual rules, all and recommend presets in top-level and group-level configs is now correctly respected. More details can be seen in (#2072) (#2028). Contributed by @Sec-ant

Formatter

Bug fixes

Fix #1661. Now nested conditionals are aligned with Prettier's logic, and won't contain mixed spaces and tabs. Contributed by @ematipico

JavaScript APIs

Enhancements

Support applying lint fixes when calling the lintContent method of the Biome class (#1956). Contributed by @mnahkies

Linter

Bug fixes

Rule noUndeclaredDependencies now also validates peerDependencies and optionalDependencies (#2122). Contributed by @Sec-ant
Rule noUndeclaredDependencies won't check declare module statements anymore (#2123). Contributed by @Sec-ant
Fix #1925. The fix for useOptionalChain would sometimes suggest an incorrect fix that discarded optional chaining operators on the left-hand side of logical expressions. These are now preserved. Contributed by @arendjr
Rule noUndeclaredVariables now also checks for worker globals (#2121). Contributed by @Sec-ant

LSP

Bug fixes

Correctly parse .jsonc files. Contributed by @Sec-ant
Correctly resolve external extends configs. Contributed by @Sec-ant

`v1.6.1`

Compare Source

CLI

Bug fixes

CLI is now able to automatically search and resolve biome.jsonc (#2008). Contributed by @Sec-ant
Fix a false positive where some files were counted as "fixed" even though they weren't modified. Contributed by @ematipico

Configuration

Bug fixes

json.formatter.trailingCommas option now works in overrides (#2009). Contributed by @Sec-ant

Linter

New features

Add rule noDoneCallback, this rule checks the function parameter of hooks & tests for use of the done argument, suggesting you return a promise instead. Contributed by @vasucp1207
```
beforeEach(done => {
  // ...
});
```

Bug fixes

useJsxKeyInIterable now recognizes function bodies wrapped in parentheses (#2011). Contributed by @Sec-ant
useShorthandFunctionType now preserves type parameters of generic interfaces when applying fixes (#2015). Contributed by @Sec-ant
Code fixes of useImportType and useExportType now handle multiline statements (#2041). Contributed by @Conaclos
noRedeclare no longer reports type parameter and parameter with identical names (#1992).

The following code is no longer reported:
```
function f<a>(a: a) {}
```
Contributed by @Conaclos
noRedeclare now reports duplicate type parameters in a same declaration.

The following type parameters are now reported as a redeclaraion:
```
function f<T, T>() {}
```
Contributed by @Conaclos
noUndeclaredDependencies now recognizes imports of subpath exports.

E.g., the following import statements no longer report errors if @mui/material and tailwindcss are installed as dependencies:
```
import Button from "@&#8203;mui/material/Button";
import { fontFamily } from "tailwindcss/defaultTheme";
```
Contributed by @Sec-ant

Parser

Bug fixes

JavaScript lexer is now able to lex regular expression literals with escaped non-ascii chars (#1941).

Contributed by @Sec-ant

`v1.6.0`

Compare Source

Analyzer

New features

Add partial for .astro files. Biome is able to sort imports inside the frontmatter of the Astro files. Contributed by @ematipico

`v1.5.3`

Compare Source

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

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

`v1.5.2`

Compare Source

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

`v1.5.1`

Compare Source

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

`v1.5.0`

Compare Source

Biome now scores 97% compatibility with Prettier and features more than 180 linter rules.

Analyzer

CLI

New features

Biome now shows a diagnostic when it encounters a protected file. Contributed by @ematipico
The command biome migrate now updates the $schema if there's an outdated version.
The CLI now takes in consideration the .gitignore in the home directory of the user, if it exists. Contributed by @ematipico
The biome ci command is now able to print GitHub Workflow Commands when there are diagnostics in our code. Contributed by @nikeee This might require setting the proper permissions on your GitHub action:
```
permissions:
  pull-requests: write
```
The commands format, lint, check and ci now accept two new arguments: --changed and --since. Use these options with the VCS integration is enabled to process only the files that were changed. Contributed by @simonxabris
```
bi
```

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Nov 27 '23 19:11 renovate[bot]

Performance Comparison Report

Current: HEAD (a2609b9bdbc330f8957860e12d7a40f29e04ddff) - 2024-08-08 03:48:27Z
Baseline: main (2f8d9fe415e605e118a1e4b648c78cc06205f699) - 2024-08-08 03:47:25Z

Significant Changes To Duration

There are no entries

Meaningless Changes To Duration

Show entries

Name	Type	Duration	Count
Perf test Renders markdown	render	57.5 ms → 56.6 ms (-0.9 ms, -1.5%)	1 → 1

Show details

Name	Type	Duration	Count
Perf test Renders markdown	render	Baseline Mean: 57.5 ms Stdev: 3.6 ms (6.3%) Runs: 66.1 60.5 59.7 57.1 56.0 55.5 55.2 55.2 55.1 54.7 Current Mean: 56.6 ms Stdev: 3.3 ms (5.8%) Runs: 64.5 60.7 55.7 55.6 55.6 55.3 54.8 54.8 54.7 54.6	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1

Changes To Count

There are no entries

Added Scenarios

There are no entries

Removed Scenarios

There are no entries

Generated by :no_entry_sign: dangerJS against 5e0a29e513a6823eb125eab5d61aff91f2864c1c

Nov 27 '23 19:11 github-actions[bot]