chore(deps): update dependency @biomejs/biome to v1.8.2 #7

Renovate [BOT] · 2024-06-25T14:09:09Z

Renovate [BOT] commented

2024-06-25 14:09:09 +00:00

This PR contains the following updates:

Package	Type	Update	Change
@biomejs/biome (source)	devDependencies	minor	`1.7.3` -> `1.8.2`

Release Notes

biomejs/biome (@biomejs/biome)

`v1.8.2`

Compare Source

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/useValidAutocomplete. Contributed by @unvalley

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

`v1.8.1`

Compare Source

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

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

`v1.8.0`

Compare Source

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 oevrrides --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/noUnknownSelectorPseudoElement. #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

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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@biomejs/biome](https://biomejs.dev) ([source](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome)) | devDependencies | minor | [`1.7.3` -> `1.8.2`](https://renovatebot.com/diffs/npm/@biomejs%2fbiome/1.7.3/1.8.2) | --- ### Release Notes <details> <summary>biomejs/biome (@biomejs/biome)</summary> ### [`v1.8.2`](https://github.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v182-2024-06-20) [Compare Source](https://github.com/biomejs/biome/compare/39db99b1cd087d6aa46ecfecba6adbfa0d45a303...54b4c9a39078836843ef363bb6986fad74834480) ##### CLI ##### Bug fixes - Fix [#3201](https://github.com/biomejs/biome/issues/3201) by correctly injecting the source code of the file when printing the diagnostics. Contributed by [@ematipico](https://github.com/ematipico) - Fix [#3179](https://github.com/biomejs/biome/issues/3179) where comma separators are not correctly removed after running `biome migrate` and thus choke the parser. Contributed by [@Sec-ant](https://github.com/Sec-ant) - Fix [#3232](https://github.com/biomejs/biome/issues/3232) by correctly using the colors set by the user. Contributed by [@ematipico](https://github.com/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: ```block Checked 2 files in <TIME>. No fixes needed. Found 2 errors. ``` The new message suits better in these cases. Contributed by [@Sec-ant](https://github.com/Sec-ant) ##### Configuration ##### Bug fixes - Don't conceal previous overrides ([#3176](https://github.com/biomejs/biome/issues/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. ```json { "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](https://github.com/Conaclos) ##### Formatter ##### Bug fixes - Fix [#3103](https://github.com/biomejs/biome/issues/3103) by correctly resolving CSS formatter options. Contributed by [@ah-yu](https://github.com/ah-yu) - Fix [#3192](https://github.com/biomejs/biome/issues/3192) don't add an extra whitespace within :has. Contributed by [@denbezrukov](https://github.com/denbezrukov) ##### JavaScript APIs ##### Bug fixes - Fix a regression introduced by the release of `v1.8.0` ##### Linter ##### New features - Add [nursery/useValidAutocomplete](https://biomejs.dev/linter/rules/use-valid-autocomplete/). Contributed by [@unvalley](https://github.com/unvalley) ##### Bug fixes - Add [nursery/noShorthandPropertyOverrides](https://biomejs.dev/linter/rules/no-shorthand-property-overrides). [#2958](https://github.com/biomejs/biome/issues/2958) Contributed by [@neokidev](https://github.com/neokidev) - Fix \[[#3084](https://github.com/biomejs/biome/issues/3084)] false positive by correctly recognize parenthesized return statement. Contributed by [@unvalley](https://github.com/unvalley) - [useImportExtensions](https://biomejs.dev/linter/rules/use-import-extensions/) now suggests a correct fix for `import '.'` and `import './.'`. Contributed by [@minht11](https://github.com/minht11) - Fix [useDateNow](https://biomejs.dev/linter/rules/use-date-now/) false positive when new Date object has arguments `new Date(0).getTime()`. Contributed by [@minht11](https://github.com/minht11). - The [`noUnmatchableAnbSelector`](https://biomejs.dev/linter/rules/no-unmatchable-anb-selector/) rule is now able to catch unmatchable `an+b` selectors like `0n+0` or `-0n+0`. Contributed by [@Sec-ant](https://github.com/Sec-ant). - The [`useHookAtTopLevel`](https://biomejs.dev/linter/rules/use-hook-at-top-level/) rule now recognizes properties named as hooks like `foo.useFoo()`. Contributed by [@ksnyder9801](https://github.com/ksnyder9801) - Fix [#3092](https://github.com/biomejs/biome/issues/3092), prevent warning for `Custom properties (--*)`. Contributed by [@chansuke](https://github.com/chansuke) - Fix a false positive in the [`useLiteralKeys`](https://biomejs.dev/linter/rules/use-literal-keys/) rule. ([#3160](https://github.com/biomejs/biome/issues/3160)) This rule now ignores the following kind of computed member name: ```js const a = { [`line1 line2`]: true, }; ``` Contributed by [@Sec-ant](https://github.com/Sec-ant) - The [noUnknownProperty](https://biomejs.dev/linter/rules/no-unknown-property/) rule now ignores the `composes` property often used in css modules. [#3000](https://github.com/biomejs/biome/issues/3000) Contributed by [@chansuke](https://github.com/chansuke) - Fix false positives of the [useExhaustiveDependencies](https://biomejs.dev/linter/rules/use-exhaustive-dependencies/) rule. The component itself is considered stable when it is used recursively inside a hook closure defined inside of it: ```jsx 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](https://github.com/Sec-ant) - Fix missing `withDefaults` macro in vue files for globals variables. Contributed by [@Shyam-Chen](https://github.com/Shyam-Chen) ##### Parser ##### Bug fixes - Fix CSS modules settings mapping. Contributed by [@denbezrukov](https://github.com/denbezrukov) ### [`v1.8.1`](https://github.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v181-2024-06-10) [Compare Source](https://github.com/biomejs/biome/compare/378c05edd47608a1b8cba725564c807b2e772bd6...39db99b1cd087d6aa46ecfecba6adbfa0d45a303) ##### CLI ##### Bug fixes - Fix [#3069](https://github.com/biomejs/biome/issues/3069), prevent overwriting paths when using `--staged` or `--changed` options. Contributed by [@unvalley](https://github.com/unvalley) - Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by [@uncenter](https://github.com/uncenter) ##### Configuration ##### Bug fixes - Fix [#3067](https://github.com/biomejs/biome/issues/3067), by assigning the correct default value to `indentWidth`. Contributed by [@ematipico](https://github.com/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](https://github.com/biomejs/biome/issues/3061). Contributed by [@denbezrukov](https://github.com/denbezrukov) - Fix [#3068](https://github.com/biomejs/biome/issues/3068) where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by [@denbezrukov](https://github.com/denbezrukov) - Fix the formatting of CSS grid layout properties. Contributed by [@denbezrukov](https://github.com/denbezrukov) ##### Linter ##### Bug fixes - The `noEmptyBlock` css lint rule now treats empty blocks containing comments as valid ones. Contributed by [@Sec-ant](https://github.com/Sec-ant) - [useLiteralKeys](https://biomejs.dev/linter/rules/use-literal-keys/) no longer reports quoted member names ([#3085](https://github.com/biomejs/biome/issues/3085)). Previously [useLiteralKeys](https://biomejs.dev/linter/rules/use-literal-keys/) reported quoted member names that can be unquoted. For example, the rule suggested the following fix: ```diff - const x = { "prop": 0 }; + const x = { prop: 0 }; ``` This conflicted with the option [quoteProperties](https://biomejs.dev/reference/configuration/#javascriptformatterquoteproperties) of our formatter. The rule now ignores quoted member names. Contributed by [@Conaclos](https://github.com/Conaclos) - [noEmptyInterface](https://biomejs.dev/linter/rules/no-empty-interface/) now ignores empty interfaces in ambient modules ([#3110](https://github.com/biomejs/biome/issues/3110)). Contributed by [@Conaclos](https://github.com/Conaclos) - [noUnusedVariables](https://biomejs.dev/linter/rules/no-unused-variables/) and [noUnusedFunctionParameters](https://biomejs.dev/linter/rules/no-unused-function-parameters/) no longer report the parameters of a constructor type ([#3135](https://github.com/biomejs/biome/issues/3135)). Previously, `arg` was reported as unused in a constructor type like: ```ts export type Classlike = new (arg: unknown) => string; ``` Contributed by [@Conaclos](https://github.com/Conaclos) - [noStringCaseMismatch](https://biomejs.dev/linter/rules/no-string-case-mismatch/) now ignores escape sequences ([#3134](https://github.com/biomejs/biome/issues/3134)). The following code is no longer reported by the rule: ```js s.toUpperCase() === "\u001b"; ``` Contributed by [@Conaclos](https://github.com/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](https://github.com/denbezrukov) - Fix [#3055](https://github.com/biomejs/biome/issues/3055) CSS: Layout using named grid lines is now correctly parsed. Contributed by [@denbezrukov](https://github.com/denbezrukov) - Fix [#3091](https://github.com/biomejs/biome/issues/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](https://github.com/denbezrukov) ### [`v1.8.0`](https://github.com/biomejs/biome/blob/HEAD/CHANGELOG.md#180-2024-06-04) [Compare Source](https://github.com/biomejs/biome/compare/b9f90b7ee63506a1995bc29f4e389efec25a1525...378c05edd47608a1b8cba725564c807b2e772bd6) ##### 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](https://github.com/biomejs/biome/issues/2509). Contributed by [@arendjr](https://github.com/arendjr) ##### Enhancements - Assume `Astro` object is always a global when processing `.astro` files. Contributed by [@minht11](https://github.com/minht11) - Assume Vue compiler macros are globals when processing `.vue` files. ([#2771](https://github.com/biomejs/biome/pull/2771)) Contributed by [@dyc3](https://github.com/dyc3) ##### CLI ##### New features - New `clean` command. Use this new command to clean after the `biome-logs` directory, and remove all the log files. ```shell biome clean ``` - Add two new options `--only` and `--skip` to the command `biome lint` ([#58](https://github.com/biomejs/biome/issues/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. ```shell 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. ```shell biome lint --skip=style --skip=suspicious/noExplicitAny ``` You can also use `--only` and `--skip` together. `--skip` oevrrides `--only`. The following command executes only the rules from the `style` group, but the `style/useNamingConvention` rule. ```shell biome lint --only=style --skip=style/useNamingConvention ``` These options are compatible with other options such as `--write` (previously `--apply`), and `--reporter`. Contributed by [@Conaclos](https://github.com/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](https://github.com/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`: ```shell biome check --css-formatter-enabled=true --css-linter-enabled=true ./ ``` Contributed by [@ematipico](https://github.com/ematipico) - Add new CLI options to control the CSS formatting. Check the [CLI reference page](https://biomejs.dev/reference/cli/) for more details. Contributed by [@ematipico](https://github.com/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`. ```shell 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](https://github.com/unvalley) ##### Enhancements - Biome now executes commands (lint, format, check and ci) on the working directory by default. [#2266](https://github.com/biomejs/biome/issues/2266) Contributed by [@unvalley](https://github.com/unvalley) ```diff - 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](https://git-scm.com/docs/gitignore#\_pattern_format). 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](https://github.com/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](https://github.com/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](https://github.com/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](https://github.com/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](https://github.com/ematipico) - Add a new `--reporter` called `github`. This reporter will print diagnostics using [GitHub workflow commands](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#about-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](https://github.com/ematipico) - Add a new `--reporter` called `junit`. This reporter will print diagnostics using [GitHub workflow commands](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#about-workflow-commands): ```xml <?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's type is not allowed to evolve implicitly, leading to potential any types.">line 7, col 4, This variable's type is not allowed to evolve implicitly, leading to potential any types.</failure> </testcase> </testsuite> </testsuites> ``` Contributed by [@ematipico](https://github.com/ematipico) ##### Bug fixes - Fix [#3024](https://github.com/biomejs/biome/issues/3024), where running `biome init` would create `biome.json` even if `biome.jsonc` already exists. Contributed by [@minht11](https://github.com/minht11) ##### Configuration ##### New features - Add an rule option `fix` to override the code fix kind of a rule ([#2882](https://github.com/biomejs/biome/issues/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. ```json { "linter": { "rules": { "correctness": { "noUnusedVariables": { "level": "error", "fix": "none" }, "style": { "useConst": { "level": "warn", "fix": "unsafe" }, "useTemplate": { "level": "warn", "fix": "safe" } } } } } } ``` Contributed by [@Conaclos](https://github.com/Conaclos) - Add option `javascript.linter.enabled` to control the linter for JavaScript (and its super languages) files. Contributed by [@ematipico](https://github.com/ematipico) - Add option `json.linter.enabled` to control the linter for JSON (and its super languages) files. Contributed by [@ematipico](https://github.com/ematipico) - Add option `css.linter.enabled` to control the linter for CSS (and its super languages) files. Contributed by [@ematipico](https://github.com/ematipico) - Add option `css.formatter`, to control the formatter options for CSS (and its super languages) files. Contributed by [@ematipico](https://github.com/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`: ```json { "linter": { "rules": { "suspicious": { "noDebugger": "info" } } } } ``` Contributed by [@ematipico](https://github.com/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](https://github.com/biomejs/biome/pull/2492). Contributed by [@Sec-ant](https://github.com/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](https://github.com/biomejs/biome/issues/2924). Contributed by [@dyc3](https://github.com/dyc3) - Fix [#2990](https://github.com/biomejs/biome/issues/2990), now Biome doesn't add a trailing comma when formatting `biome.json`. Contributed by [@dyc3](https://github.com/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](https://github.com/ematipico) ##### Bug fixes - Fixes [#2781](https://github.com/biomejs/biome/issues/2781), by correctly computing the configuration to apply to a specific file. Contributed by [@ematipico](https://github.com/ematipico) ##### Formatter ##### Bug fixes - Fix [#2470](https://github.com/biomejs/biome/issues/2470) by avoid introducing linebreaks in single line string interpolations. Contributed by [@ah-yu](https://github.com/ah-yu) - Resolve deadlocks by narrowing the scope of locks. Contributed by [@mechairoi](https://github.com/mechairoi) - Fix [#2782](https://github.com/biomejs/biome/issues/2782) by computing the enabled rules by taking the override settings into consideration. Contributed by [@ematipico](https://github.com/ematipico) - Fix \[https://github.com/biomejs/biome/issues/2877] by correctly handling line terminators in JSX string. Contributed by [@ah-yu](https://github.com/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: - [useImportRestrictions](https://biomejs.dev/linter/rules/use-import-restrictions/) - [noNodejsModules](https://biomejs.dev/linter/rules/no-nodejs-modules/) - [useArrayLiterals](https://biomejs.dev/linter/rules/use-array-literals/) - [noConstantMathMinMaxClamp](https://biomejs.dev/linter/rules/no-constant-math-min-max-clamp/) - [noFlatMapIdentity](https://biomejs.dev/linter/rules/no-flat-map-identity/) ##### New features - Add [nursery/useDateNow](https://biomejs.dev/linter/rules/use-date-now/). Contributed by [@minht11](https://github.com/minht11) - Add [nursery/useErrorMessage](https://biomejs.dev/linter/rules/use-error-message/). Contributed by [@minht11](https://github.com/minht11) - Add [nursery/useThrowOnlyError](https://biomejs.dev/linter/rules/use-throw-only-error/). Contributed by [@minht11](https://github.com/minht11) - Add [nursery/useImportExtensions](https://biomejs.dev/linter/rules/use-import-extensions/). Contributed by [@minht11](https://github.com/minht11) - [useNamingConvention](https://biomejs.dev/linter/rules/use-naming-convention/) now supports an option to enforce custom conventions ([#1900](https://github.com/biomejs/biome/issues/1900)). For example, you can enforce the use of a prefix for private class members: ```json { "linter": { "rules": { "style": { "useNamingConvention": { "level": "error", "options": { "conventions": [ { "selector": { "kind": "classMember", "modifiers": ["private"] }, "match": "_(.*)", "formats": ["camelCase"] } ] } } } } } } ``` Please, find more details in the [rule documentation](https://biomejs.dev/linter/rules/use-naming-convention/#options). Contributed by [@Conaclos](https://github.com/Conaclos) - Add [nursery/useNumberToFixedDigitsArgument](https://biomejs.dev/linter/rules/use-number-to-fixed-digits-argument/). Contributed by [@minht11](https://github.com/minht11) - Add [nursery/useThrowNewError](https://biomejs.dev/linter/rules/use-throw-new-error/). Contributed by [@minht11](https://github.com/minht11) - Add [nursery/useTopLevelRegex](https://biomejs.dev/linter/rules/use-top-level-regex), which enforces defining regular expressions at the top level of a module. [#2148](https://github.com/biomejs/biome/issues/2148) Contributed by [@dyc3](https://github.com/dyc3). - Add [nursery/noCssEmptyBlock](https://biomejs.dev/linter/rules/no-css-empty-block). [#2513](https://github.com/biomejs/biome/pull/2513) Contributed by [@togami2864](https://github.com/togami2864) - Add [nursery/noDuplicateAtImportRules](https://biomejs.dev/linter/rules/no-duplicate-at-import-rules). [#2658](https://github.com/biomejs/biome/pull/2658) Contributed by [@DerTimonius](https://github.com/DerTimonius) - Add [nursery/noDuplicateFontNames](https://biomejs.dev/linter/rules/no-duplicate-font-names). [#2308](https://github.com/biomejs/biome/pull/2308) Contributed by [@togami2864](https://github.com/togami2864) - Add [nursery/noDuplicateSelectorsKeyframeBlock](https://biomejs.dev/linter/rules/no-duplicate-selectors-keyframe-block). [#2534](https://github.com/biomejs/biome/pull/2534) Contributed by [@isnakode](https://github.com/isnakode) - Add [nursery/noImportantInKeyframe](https://biomejs.dev/linter/rules/no-important-in-keyframe). [#2542](https://github.com/biomejs/biome/pull/2542) Contributed by [@isnakode](https://github.com/isnakode) - Add [nursery/noInvalidPositionAtImportRule](https://biomejs.dev/linter/rules/no-invalid-position-at-import-rule). [#2717](https://github.com/biomejs/biome/issues/2717) Contributed by [@t-shiratori](https://github.com/t-shiratori) - Add [nursery/noUnknownFunction](https://biomejs.dev/linter/rules/no-unknown-function). [#2570](https://github.com/biomejs/biome/pull/2570) Contributed by [@neokidev](https://github.com/neokidev) - Add [nursery/noUnknownMediaFeatureName](https://biomejs.dev/linter/rules/no-unknown-media-feature-name). [#2751](https://github.com/biomejs/biome/issues/2751) Contributed by [@Kazuhiro-Mimaki](https://github.com/Kazuhiro-Mimaki) - Add [nursery/noUnknownProperty](https://biomejs.dev/linter/rules/no-unknown-property). [#2755](https://github.com/biomejs/biome/pull/2755) Contributed by [@chansuke](https://github.com/chansuke) - Add [nursery/noUnknownSelectorPseudoElement](https://biomejs.dev/linter/rules/no-unknown-selector-pseudo-element). [#2655](https://github.com/biomejs/biome/issues/2655) Contributed by [@keita-hino](https://github.com/keita-hino) - Add [nursery/noUnknownUnit](https://biomejs.dev/linter/rules/no-unknown-unit). [#2535](https://github.com/biomejs/biome/issues/2535) Contributed by [@neokidev](https://github.com/neokidev) - Add [nursery/noUnmatchableAnbSelector](https://biomejs.dev/linter/rules/no-unmatchable-anb-selector). [#2706](https://github.com/biomejs/biome/issues/2706) Contributed by [@togami2864](https://github.com/togami2864) - Add [nursery/useGenericFontNames](https://biomejs.dev/linter/rules/use-generic-font-names). [#2573](https://github.com/biomejs/biome/pull/2573) Contributed by [@togami2864](https://github.com/togami2864) - Add [nursery/noYodaExpression](https://biomejs.dev/linter/rules/no-yoda-expression/). Contributed by [@michellocana](https://github.com/michellocana) - Add [nursery/noUnusedFunctionParameters](https://biomejs.dev/linter/rules/no-unused-function-parameters/) Contributed by [@printfn](https://github.com/printfn) - Add [nursery/UseSemanticElements](https://biomejs.dev/linter/rules/use-semantic-elements/). Contributed by [@fujiyamaorange](https://github.com/fujiyamaorange) ##### Enhancements - Add a code action for [noConfusingVoidType](https://biomejs.dev/linter/rules/no-confusing-void-type/) and improve the diagnostics. The rule now suggests using `undefined` instead of `void` in confusing places. The diagnosis is also clearer. Contributed by [@Conaclos](https://github.com/Conaclos) - Improve code action for [nursery/noUselessUndefinedInitialization](https://biomejs.dev/linter/rules/no-useless-undefined-initialization/) 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](https://github.com/lutaok) - Make [useExhaustiveDependencies](https://biomejs.dev/linter/rules/use-exhaustive-dependencies/) report duplicate dependencies. Contributed by [@tunamaguro](https://github.com/tunamaguro) - Rename `noEvolvingAny` into `noEvolvingTypes` ([#48](https://github.com/biomejs/website/issues/48)). Contributed by [@Conaclos](https://github.com/Conaclos) ##### Bug fixes - [noUndeclaredVariables](https://biomejs.dev/linter/rules/no-undeclared-variables/) and [noUnusedImports](https://biomejs.dev/linter/rules/no-unused-imports) now correctly handle import namespaces ([#2796](https://github.com/biomejs/biome/issues/2796)). Previously, Biome bound unqualified type to import namespaces. Import namespaces can only be used as qualified names in a type (ambient) context. ```ts // 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](https://github.com/Conaclos) - [noUndeclaredVariables](https://biomejs.dev/linter/rules/no-undeclared-variables/) now correctly handle ambient computed member names ([#2975](https://github.com/biomejs/biome/issues/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. ```ts import type { NAME } from "./constants.js"; type X = { [NAME]: number }; ``` Contributed by [@Conaclos](https://github.com/Conaclos) - [noUndeclaredVariables](https://biomejs.dev/linter/rules/no-undeclared-variables/) now ignores `this` in JSX components ([#2636](https://github.com/biomejs/biome/issues/2636)). The rule no longer reports `this` as undeclared in following code. ```jsx import { Component } from 'react'; export class MyComponent extends Component { render() { return <this.foo /> } } ``` Contributed by [@printfn](https://github.com/printfn) and [@Conaclos](https://github.com/Conaclos) - `useJsxKeyInIterable` now handles more cases involving fragments. See the snippets below. Contributed by [@dyc3](https://github.com/dyc3) ```jsx // 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](https://github.com/biomejs/biome/issues/2599) Contributed by [@dyc3](https://github.com/dyc3) ```js // now valid z.object({}) .describe('') .describe('') .describe('') .describe('') .describe('') .describe(''); ``` - `noEmptyBlockStatements` no longer reports empty constructors using typescript parameter properties. [#3005](https://github.com/biomejs/biome/issues/3005) Contributed by [@dyc3](https://github.com/dyc3) - `noEmptyBlockStatements` no longer reports empty private or protected constructors. Contributed by [@dyc3](https://github.com/dyc3) - [noExportsInTest](https://biomejs.dev/linter/rules/no-exports-in-test/) rule no longer treats files with in-source testing as test files https://github.com/biomejs/biome/issues/2859. Contributed by [@ah-yu](https://github.com/ah-yu) - [useSortedClasses](https://biomejs.dev/linter/rules/use-sorted-classes/) 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](https://biomejs.dev/linter/rules/no-undeclared-dependencies/) is correctly triggered when running `biome ci`. Contributed by [@ematipico](https://github.com/ematipico) - [noUnusedVariables](https://biomejs.dev/linter/rules/no-unused-variables/) no longer panics when a certain combination of characters is typed. Contributed by [@ematipico](https://github.com/ematipico) - [noUndeclaredVariables](https://biomejs.dev/linter/rules/no-undeclared-variables/) no logger alerts on `arguments` object in a function scope. Contributed by [@ah-yu](https://github.com/ah-yu) ##### Parser ##### Enhancements - `lang="tsx"` is now supported in Vue Single File Components. [#2765](https://github.com/biomejs/biome/issues/2765) Contributed by [@dyc3](https://github.com/dyc3) ##### Bug fixes - The `const` modifier for type parameters is now accepted for TypeScript `new` signatures ([#2825](https://github.com/biomejs/biome/issues/2825)). The following code is now correctly parsed: ```ts interface I { new<const T>(x: T): T } ``` Contributed by [@Conaclos](https://github.com/Conaclos) - Some invalid TypeScript syntax caused the Biome parser to crash. The following invalid syntax no longer causes the Biome parser to crash: ```ts declare using x: null; declare qwait using x: null; ``` Contributed by [@Conaclos](https://github.com/Conaclos) </details> --- ### 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 [Renovate Bot](https://github.com/renovatebot/renovate).

Renovate [BOT] added 1 commit 2024-06-25 14:09:10 +00:00

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

Build Docker Image / build_docker (push) Failing after 2m41s

Details

Lint / run (push) Failing after 37s

Details

Build, check & Test / run (push) Successful in 8m49s

Details

Delete Packages / Delete the package on a closed Pull Request (pull_request) Failing after 6s

Details

Delete Packages / Delete the package on a deleted branch (pull_request) Has been skipped

Details

75f435ca74

Florian Bouillon merged commit ae453eaa89 into master

2024-06-25 14:25:57 +00:00

Florian Bouillon deleted branch renovate/biomejs-biome-1.x-lockfile

2024-06-25 14:25:57 +00:00

Florian Bouillon referenced this issue from a commit

2024-06-25 14:25:58 +00:00

chore(deps): update dependency @biomejs/biome to v1.8.2 (#7)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: avior/template-web-astro#7