Update dependency @biomejs/biome to v1.8.3

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	1.8.1 -> 1.8.3

---

Release Notes

biomejs/biome (@​biomejs/biome)

### [`v1.8.3`](https://togithub.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v183-2022-06-27) [Compare Source](https://togithub.com/biomejs/biome/compare/54b4c9a39078836843ef363bb6986fad74834480...c28d5978c1440b3ae184d1cc354233711abf8a8e) ##### CLI ##### Bug fixes - Fix [#​3104](https://togithub.com/biomejs/biome/issues/3104) by suppressing node warnings when using `biome migrate`. Contributed by [@​SuperchupuDev](https://togithub.com/SuperchupuDev) - Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions ([#​3148](https://togithub.com/biomejs/biome/issues/3148)). Contributed by [@​Sec-ant](https://togithub.com/Sec-ant) ##### Parser ##### Bug fixes - Implement [CSS unicode range](https://togithub.com/biomejs/biome/pull/3251). Contributed by [@​denbezrukov](https://togithub.com/denbezrukov) ##### Formatter ##### Bug fixes - Fix [#​3184](https://togithub.com/biomejs/biome/issues/3184) CSS formatter converts custom identifiers to lowercase. Contributed by [@​denbezrukov](https://togithub.com/denbezrukov) - Fix [#​3256](https://togithub.com/biomejs/biome/issues/3256) constant crashes when editing css files [#​3256](https://togithub.com/biomejs/biome/issues/3256). Contributed by [@​denbezrukov](https://togithub.com/denbezrukov) ##### Linter ##### New features - Add `nursery/useDeprecatedReason` rule. Contributed by [@​vohoanglong0107](https://togithub.com/vohoanglong0107). - Add [nursery/noExportedImports](https://biomejs.dev/linter/rules/no-exported-imports/). Contributed by [@​Conaclos](https://togithub.com/Conaclos) ##### Bug fixes - `useConsistentArrayType` and `useShorthandArrayType` now ignore `Array` in the `extends` and `implements` clauses. Fix [#​3247](https://togithub.com/biomejs/biome/issues/3247). Contributed by [@​Conaclos](https://togithub.com/Conaclos) - Fixes [#​3066](https://togithub.com/biomejs/biome/issues/3066) by taking into account the dependencies declared in the `package.json`. Contributed by [@​ematipico](https://togithub.com/ematipico) - The code action of the `useArrowFunction` rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes [#​3292](https://togithub.com/biomejs/biome/issues/3292). Contributed by [@​Sec-ant](https://togithub.com/Sec-ant) ##### Enhancements - Enhance tailwind sorting lint rule [#​1274](https://togithub.com/biomejs/biome/issues/1274) with variant support. Every preconfigured variant is assigned a `weight` that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting `weight` is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. `has-[.custom-class]`, `group-[:checked]`) are also supported and they take the `weight` of their base variant name the custom value attached (e.g. `has-[.custom-class]` takes `has` weight). Arbitrary variants (e.g. `[&nth-child(2)]`) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. `sm:`, `max-md:`, `min-lg:`) are not supported yet. Contributed by [@​lutaok](https://togithub.com/lutaok) ### [`v1.8.2`](https://togithub.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v182-2024-06-20) [Compare Source](https://togithub.com/biomejs/biome/compare/39db99b1cd087d6aa46ecfecba6adbfa0d45a303...54b4c9a39078836843ef363bb6986fad74834480) ##### CLI ##### Bug fixes - Fix [#​3201](https://togithub.com/biomejs/biome/issues/3201) by correctly injecting the source code of the file when printing the diagnostics. Contributed by [@​ematipico](https://togithub.com/ematipico) - Fix [#​3179](https://togithub.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://togithub.com/Sec-ant) - Fix [#​3232](https://togithub.com/biomejs/biome/issues/3232) by correctly using the colors set by the user. Contributed by [@​ematipico](https://togithub.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 . No fixes needed. Found 2 errors. ``` The new message suits better in these cases. Contributed by [@​Sec-ant](https://togithub.com/Sec-ant) ##### Configuration ##### Bug fixes - Don't conceal previous overrides ([#​3176](https://togithub.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://togithub.com/Conaclos) ##### Formatter ##### Bug fixes - Fix [#​3103](https://togithub.com/biomejs/biome/issues/3103) by correctly resolving CSS formatter options. Contributed by [@​ah-yu](https://togithub.com/ah-yu) - Fix [#​3192](https://togithub.com/biomejs/biome/issues/3192) don't add an extra whitespace within :has. Contributed by [@​denbezrukov](https://togithub.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://togithub.com/unvalley) ##### Bug fixes - Add [nursery/noShorthandPropertyOverrides](https://biomejs.dev/linter/rules/no-shorthand-property-overrides). [#​2958](https://togithub.com/biomejs/biome/issues/2958) Contributed by [@​neokidev](https://togithub.com/neokidev) - Fix \[[#​3084](https://togithub.com/biomejs/biome/issues/3084)] false positive by correctly recognize parenthesized return statement. Contributed by [@​unvalley](https://togithub.com/unvalley) - [useImportExtensions](https://biomejs.dev/linter/rules/use-import-extensions/) now suggests a correct fix for `import '.'` and `import './.'`. Contributed by [@​minht11](https://togithub.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://togithub.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://togithub.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://togithub.com/ksnyder9801) - Fix [#​3092](https://togithub.com/biomejs/biome/issues/3092), prevent warning for `Custom properties (--*)`. Contributed by [@​chansuke](https://togithub.com/chansuke) - Fix a false positive in the [`useLiteralKeys`](https://biomejs.dev/linter/rules/use-literal-keys/) rule. ([#​3160](https://togithub.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://togithub.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://togithub.com/biomejs/biome/issues/3000) Contributed by [@​chansuke](https://togithub.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(() => , []); return

{children}

; } ``` 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://togithub.com/Sec-ant) - Fix missing `withDefaults` macro in vue files for globals variables. Contributed by [@​Shyam-Chen](https://togithub.com/Shyam-Chen) ##### Parser ##### Bug fixes - Fix CSS modules settings mapping. Contributed by [@​denbezrukov](https://togithub.com/denbezrukov)

---

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.

[zoriya]

@onedr0p Do you think this would be possible to also update the bione version on front/package.json with this PR (and run it). This would make Biome update PR more interesting than the one char change from the config file.

If this is not possible should we simply disable those PR and use the cli to update this version?

[onedr0p]

Sure we might have to revisit ignoring all frontend updates since it's a flat ignore of the entire folder.

[onedr0p]

What does the manual (CLI) process entail? We can update the ignorePaths in the config like so

"ignorePaths": [
  "**/front/.yarn/**",
  "**/front/apps/**",
  "**/front/packages/**",
],

This way the front/packages.json will get picked up by renovate but unsure what you expect and I am not sure if renovate can cover the CLI commands that need to be ran.

[zoriya]

Updating the frontend means:

• Updating everything under front/package.json (and running biome for coding style changes)
• Updating every other package
• Running expo install so it prevents the use of newer versions not yet supported
• Pin those versions to other packages needing this (to prevent package duplication)
  • Run on every platform to be sure everything will work
• Merge

I think some of those steps will always need to be done by hand but maybe renovate could help a bit.

It might be good to look at how solito does this since they prone mono-repo with both mobile and web.

[onedr0p]

It seems maybe possible using this type of config in renovate?

https://docs.renovatebot.com/configuration-options/#postupgradetasks

[zoriya]

Thats look like what we want but it can only be used on self hosted renovate. Should we give up and keep the current approach?

[onedr0p]

Probably the latter, seems like you can just remove the custom manager for biome in the renovate config?