chore(deps): update all non-major dependencies

renovate[bot] commented 6 days ago

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`1.7.3` -> `1.8.3`	devDependencies	minor
@codemirror/autocomplete	`^6.16.2` -> `^6.16.3`	dependencies	patch
@codemirror/commands	`^6.5.0` -> `^6.6.0`	dependencies	minor
@codemirror/lint	`^6.8.0` -> `^6.8.1`	dependencies	patch
@codemirror/view	`^6.26.3` -> `^6.28.3`	dependencies	minor
@dagrejs/dagre	`^1.1.2` -> `^1.1.3`	dependencies	patch
@hookform/resolvers (source)	`^3.4.2` -> `^3.6.0`	dependencies	minor
@playwright/test (source)	`^1.44.1` -> `^1.45.0`	devDependencies	minor
@swc-jotai/react-refresh (source)	`^0.1.0` -> `^0.1.1`	devDependencies	patch
@tanstack/react-table (source)	`^8.17.3` -> `^8.19.2`	dependencies	minor
@types/node (source)	`^20.14.0` -> `^20.14.9`	devDependencies	patch
@uiw/codemirror-extensions-langs (source)	`^4.22.1` -> `^4.22.2`	dependencies	patch
@uiw/react-codemirror (source)	`^4.22.1` -> `^4.22.2`	dependencies	patch
ai (source)	`^3.1.23` -> `^3.2.16`	dependencies	minor
astral-sh/ruff-pre-commit	`v0.4.7` -> `v0.5.0`	repository	minor
biomejs/pre-commit	`v0.1.0` -> `v0.4.0`	repository	minor
copilot-node-server	`1.33.0` -> `1.37.0`	dependencies	minor
crate-ci/typos	`v1.21.0` -> `v1.22.9`	repository	minor
crate-ci/typos	`v1.21.0` -> `v1.22.9`	action	minor
cssnano	`^7.0.1` -> `^7.0.3`	dependencies	patch
jotai	`^2.8.3` -> `^2.8.4`	dependencies	patch
lucide-react (source)	`^0.383.0` -> `^0.400.0`	dependencies	minor
openapi-fetch (source)	`^0.9.7` -> `^0.10.2`	dependencies	minor
pnpm (source)	`8.15.7` -> `8.15.8`	packageManager	patch
postcss (source)	`^8.4.38` -> `^8.4.39`	devDependencies	patch
pyodide	`^0.26.0` -> `^0.26.1`	dependencies	patch
react-codemirror-merge (source)	`^4.22.1` -> `^4.22.2`	dependencies	patch
react-hook-form (source)	`^7.51.5` -> `^7.52.0`	dependencies	minor
reactflow (source)	`^11.11.3` -> `^11.11.4`	dependencies	patch
stylelint-config-standard	`^36.0.0` -> `^36.0.1`	devDependencies	patch
tailwindcss (source)	`^3.4.3` -> `^3.4.4`	devDependencies	patch
turbo (source)	`^2.0.3` -> `^2.0.6`	devDependencies	patch
vega-lite (source)	`^5.18.1` -> `^5.19.0`	dependencies	minor
vega-loader	`^4.5.1` -> `^4.5.2`	dependencies	patch
vite (source)	`^5.2.12` -> `^5.3.2`	devDependencies	minor
ws	`^8.17.0` -> `^8.17.1`	devDependencies	patch

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

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) ### [`v1.8.1`](https://togithub.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v181-2024-06-10) [Compare Source](https://togithub.com/biomejs/biome/compare/378c05edd47608a1b8cba725564c807b2e772bd6...39db99b1cd087d6aa46ecfecba6adbfa0d45a303) ##### Analyzer ##### CLI ##### Bug fixes - Fix [#3069](https://togithub.com/biomejs/biome/issues/3069), prevent overwriting paths when using `--staged` or `--changed` options. Contributed by [@unvalley](https://togithub.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://togithub.com/uncenter) ##### Configuration ##### Bug fixes - Fix [#3067](https://togithub.com/biomejs/biome/issues/3067), by assigning the correct default value to `indentWidth`. Contributed by [@ematipico](https://togithub.com/ematipico) ##### Editors ##### 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://togithub.com/biomejs/biome/issues/3061). Contributed by [@denbezrukov](https://togithub.com/denbezrukov) - Fix [#3068](https://togithub.com/biomejs/biome/issues/3068) where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by [@denbezrukov](https://togithub.com/denbezrukov) - Fix the formatting of CSS grid layout properties. Contributed by [@denbezrukov](https://togithub.com/denbezrukov) ##### JavaScript APIs ##### Linter ##### Bug fixes - The `noEmptyBlock` css lint rule now treats empty blocks containing comments as valid ones. Contributed by [@Sec-ant](https://togithub.com/Sec-ant) - [useLiteralKeys](https://biomejs.dev/linter/rules/use-literal-keys/) no longer reports quoted member names ([#3085](https://togithub.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://togithub.com/Conaclos) - [noEmptyInterface](https://biomejs.dev/linter/rules/no-empty-interface/) now ignores empty interfaces in ambient modules ([#3110](https://togithub.com/biomejs/biome/issues/3110)). Contributed by [@Conaclos](https://togithub.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://togithub.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://togithub.com/Conaclos) - [noStringCaseMismatch](https://biomejs.dev/linter/rules/no-string-case-mismatch/) now ignores escape sequences ([#3134](https://togithub.com/biomejs/biome/issues/3134)). The following code is no longer reported by the rule: ```js s.toUpperCase() === "\u001b"; ``` Contributed by [@Conaclos](https://togithub.com/Conaclos) ##### Parser ##### New features - Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by [@denbezrukov](https://togithub.com/denbezrukov) ##### Bug fixes - Fix [#3055](https://togithub.com/biomejs/biome/issues/3055) CSS: Layout using named grid lines is now correctly parsed. Contributed by [@denbezrukov](https://togithub.com/denbezrukov) - Fix [#3091](https://togithub.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://togithub.com/denbezrukov) ### [`v1.8.0`](https://togithub.com/biomejs/biome/blob/HEAD/CHANGELOG.md#180-2024-06-04) [Compare Source](https://togithub.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://togithub.com/biomejs/biome/issues/2509). Contributed by [@arendjr](https://togithub.com/arendjr) ##### Enhancements - Assume `Astro` object is always a global when processing `.astro` files. Contributed by [@minht11](https://togithub.com/minht11) - Assume Vue compiler macros are globals when processing `.vue` files. ([#2771](https://togithub.com/biomejs/biome/pull/2771)) Contributed by [@dyc3](https://togithub.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://togithub.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://togithub.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://togithub.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://togithub.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://togithub.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 -- [--unsafe] biome format -- biome migrate -- ``` The `biome --` has the same behavior as `biome --apply`. The `biome -- --unsafe` has the same behavior as `biome --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://togithub.com/unvalley) ##### Enhancements - Biome now executes commands (lint, format, check and ci) on the working directory by default. [#2266](https://togithub.com/biomejs/biome/issues/2266) Contributed by [@unvalley](https://togithub.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://togithub.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://togithub.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://togithub.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://togithub.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://togithub.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://togithub.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 line 3, col 2, Use === instead of ==. == is only allowed when comparing against `null` line 5, col 0, This is an unexpected use of the debugger statement. line 7, col 4, This variable's type is not allowed to evolve implicitly, leading to potential any types. ``` Contributed by [@ematipico](https://togithub.com/ematipico) ##### Bug fixes - Fix [#3024](https://togithub.com/biomejs/biome/issues/3024), where running `biome init` would create `biome.json` even if `biome.jsonc` already exists. Contributed by [@minht11](https://togithub.com/minht11) ##### Configuration ##### New features - Add an rule option `fix` to override the code fix kind of a rule ([#2882](https://togithub.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://togithub.com/Conaclos) - Add option `javascript.linter.enabled` to control the linter for JavaScript (and its super languages) files. Contributed by [@ematipico](https://togithub.com/ematipico) - Add option `json.linter.enabled` to control the linter for JSON (and its super languages) files. Contributed by [@ematipico](https://togithub.com/ematipico) - Add option `css.linter.enabled` to control the linter for CSS (and its super languages) files. Contributed by [@ematipico](https://togithub.com/ematipico) - Add option `css.formatter`, to control the formatter options for CSS (and its super languages) files. Contributed by [@ematipico](https://togithub.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://togithub.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://togithub.com/biomejs/biome/pull/2492). Contributed by [@Sec-ant](https://togithub.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://togithub.com/biomejs/biome/issues/2924). Contributed by [@dyc3](https://togithub.com/dyc3) - Fix [#2990](https://togithub.com/biomejs/biome/issues/2990), now Biome doesn't add a trailing comma when formatting `biome.json`. Contributed by [@dyc3](https://togithub.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://togithub.com/ematipico) ##### Bug fixes - Fixes [#2781](https://togithub.com/biomejs/biome/issues/2781), by correctly computing the configuration to apply to a specific file. Contributed by [@ematipico](https://togithub.com/ematipic

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

vercel[bot] commented 6 days ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
marimo-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 2, 2024 3:46pm
marimo-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 2, 2024 3:46pm

renovate[bot] commented 5 days ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

github-actions[bot] commented 4 days ago

🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.6.26-dev6

marimo-team / marimo