chore: update all non-major dependencies #33

renovate · 2025-08-04T00:32:25Z

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`^2.1.2` -> `^2.3.2`
@eslint/js (source)	`^9.32.0` -> `^9.38.0`
@hey-api/openapi-ts (source)	`^0.80.1` -> `^0.86.8`
@tailwindcss/vite (source)	`^4.1.11` -> `^4.1.16`
@tanstack/react-query (source)	`^5.83.0` -> `^5.90.5`
@tanstack/react-query-devtools (source)	`^5.83.0` -> `^5.90.2`
@tanstack/react-router (source)	`^1.130.2` -> `^1.133.35`
@tanstack/react-router-devtools (source)	`^1.130.2` -> `^1.133.35`
@tanstack/router-plugin (source)	`^1.130.2` -> `^1.133.35`
@types/leaflet (source)	`^1.9.20` -> `^1.9.21`
@types/luxon (source)	`^3.6.2` -> `^3.7.1`
@types/node (source)	`^22.16.5` -> `^22.18.13`
@types/react (source)	`^19.1.8` -> `^19.2.2`
@types/react-dom (source)	`^19.1.6` -> `^19.2.2`
eslint (source)	`^9.32.0` -> `^9.38.0`
eslint-plugin-react-refresh	`^0.4.20` -> `^0.4.24`
globals	`^16.3.0` -> `^16.4.0`
luxon	`^3.7.1` -> `^3.7.2`
pnpm (source)	`10` -> `10.20.0`
react (source)	`^19.1.1` -> `^19.2.0`
react-dom (source)	`^19.1.1` -> `^19.2.0`
tailwindcss (source)	`^4.1.11` -> `^4.1.16`
typescript (source)	`^5.8.3` -> `^5.9.3`
typescript-eslint (source)	`^8.38.0` -> `^8.46.2`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.3.2`

Compare Source

Patch Changes

#7859 c600618 Thanks @Netail! - Added the nursery rule noIncrementDecrement, disallows the usage of the unary operators ++ and --.
#7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome couldn't properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.
#7874 e617d36 Thanks @Bertie690! - Fixed #7230: noUselessStringConcat no longer emits false positives for multi-line strings with leading + operators.

Previously, the rule did not check for leading newlines on the + operator, emitting false positives if one occurred at the start of a line.
Notably, formatting with operatorLinebreak="before" would move the + operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting of operatorLinebreak.

Example
```
// The following code used to error if the `+` operators were at the start of lines (as opposed to the end).
// Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.
const reallyLongStringThatShouldNotError =
  "Lorem ipsum dolor sit amet consectetur adipiscing elit." +
  "Quisque faucibus ex sapien vitae pellentesque sem placerat." +
  "In id cursus mi pretium tellus duis convallis." +
  "Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";
```
#7786 33ffcd5 Thanks @daivinhtran! - Fixed #7601: Properly match Grit plugin's code snippet with only one child.
#7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

`v2.3.1`

Compare Source

Patch Changes

#7840 72afdfa Thanks @ematipico! - Fixed #7838, which caused the new --css-parse-* arguments not being recognised by the ci command.
#7789 d5b416e Thanks @fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.
#7852 bd254c7 Thanks @dyc3! - Fixed #7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.
#7872 0fe13fe Thanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.
#7866 7b2600b Thanks @dyc3! - Fixed #7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.
#7853 fe90c78 Thanks @dyc3! - Fixed #7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind's source exclude syntax: @source not "foo.css";
#7878 c9f7fe5 Thanks @ematipico! - Fixed #7857: Biome now parses <script> tags as TypeScript when analysing .astro files.
#7867 b42b718 Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.

The error message for disabled text expressions incorrectly referred
to the html.parser.textExpression option, which does not exist.
Updated it to reference the correct html.parser.interpolation option.

`v2.3.0`

Compare Source

Minor Changes

#7263 a3e3369 Thanks @arendjr! - Biome's resolver now supports baseUrl if specified in tsconfig.json.

Example

Given the following file structure:

tsconfig.json

{
  "compilerOptions": {
    "baseUrl": "./src"
  }
}

src/foo.ts

export function foo() {}

In this scenario, import { foo } from "foo"; should work regardless of the
location of the file containing the import statement.

Fixes #6432.

#7745 6fcbc07 Thanks @dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won't be emitted.
#7753 63cb7ff Thanks @ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:
```
{
+  "vcs": {
+    "enabled": true,
+    "clientKind": "git",
+    "useIgnoreFile": true
+  }
}
```
If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:
```
{
+  "files": {
+    "includes": ["**", "!!**/dist"]
+  }
}
```
#7548 85d3a3a Thanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

You can now enable or disable CSS Modules parsing directly from the command line:

biome check --css-parse-css-modules=true file.module.css
biome format --css-parse-css-modules=true file.module.css
biome lint --css-parse-css-modules=true file.module.css
biome ci --css-parse-css-modules=true file.module.css

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-tailwind-directives CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.

You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:
```
biome check --css-parse-tailwind-directives=true file.css
biome format --css-parse-tailwind-directives=true file.css
biome lint --css-parse-tailwind-directives=true file.css
biome ci --css-parse-tailwind-directives=true file.css
```
#7330 272632f Thanks @ematipico! - Updated the formatting of .svelte and .vue files. Now the indentation of the JavaScript blocks matches Prettier's:
```
<script>
- import Component from "./Component"
+   import Component from "./Component"
</script>
```
#7333 de0d2d6 Thanks @dyc3! - Implemented the indentScriptAndStyle option for vue and svelte files, with the default set to false to match Prettier's vueIndentScriptAndStyle option. When enabled, this option indents the content within <script> and <style> tags to align with the surrounding HTML structure.

It can be enabled with this configuration:
```
{
  "html": {
    "formatter": {
      "indentScriptAndStyle": true
    }
  }
}
```
Which will format this code to:
```
<script>
import Component from "./Component.vue";
</script>
```
#7359 ebbddc4 Thanks @arendjr! - Deprecated the option files.experimentalScannerIgnores in favour of force-ignore syntax in files.includes.

files.includes supports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supports force-ignoring globs by prefixing them with a double exclamation mark (!!).

The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested biome.json files.

Example

Let's take the following configuration:

{
  "files": {
    "includes": [
      "**",
      "!**/generated",
      "!!**/dist",
      "fixtures/example/dist/*.js"
    ]
  },
  "linter": {
    "domains": {
      "project": "all"
    }
  }
}

This configuration achieves the following:

Because the project domain is enabled, all supported files in the project are indexed and processed by the linter, except:
Files inside a generated folder are not processed by the linter, but they will get indexed if a file outside a generated folder imports them.
Files inside a dist folder are never indexed nor processed, not even if they are imported for any purpose, except:
When the dist folder is inside fixtures/example/, its .js files do get both indexed and processed.

In general, we now recommend using the force-ignore syntax for any folders that contain output files, such as build/ and dist/. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.

experimentalScannerIgnores will continue to work for now, but you'll see a deprecation warning if you still use it.

Run the biome migrate --write command to automatically update the configuration file.

#7698 3b6f5e3 Thanks @ematipico! - Added a new reporter named rdjson. This reporter prints diagnostics following the RDJSON format:

The following command:

biome check --reporter=rdjson

Will emit diagnostics in the following format:

{
  "source": {
    "name": "Biome",
    "url": "https://biomejs.dev"
  },
  "diagnostics": [
    {
      "code": {
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
        "value": "lint/correctness/noUnusedImports"
      },
      "location": {
        "path": "index.ts",
        "range": {
          "end": {
            "column": 11,
            "line": 0
          },
          "start": {
            "column": 7,
            "line": 0
          }
        }
      },
      "message": "This import is unused."
    },
    {
      "code": {
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
        "value": "lint/correctness/noUnusedImports"
      },
      "location": {
        "path": "index.ts",
        "range": {
          "end": {
            "column": 10,
            "line": 1
          },
          "start": {
            "column": 9,
            "line": 1
          }
        }
      },
      "message": "Several of these imports are unused."
    }
  ]
}

#7719 188a767 Thanks @cadunass! - The formatWithErrors option can now be set via CLI using the --format-with-errors flag.

This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.

Example

biome format --format-with-errors=true --write file.js

#7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-comments CLI flag to control whether comments are allowed in JSON files.

You can now enable or disable comment parsing in JSON files directly from the command line:
```
biome check --json-parse-allow-comments=true file.json
biome format --json-parse-allow-comments=true file.json
biome lint --json-parse-allow-comments=true file.json
biome ci --json-parse-allow-comments=true file.json
```
#7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-trailing-commas CLI flag to control whether trailing commas are allowed in JSON files.

You can now enable or disable trailing comma parsing in JSON files directly from the command line:
```
biome check --json-parse-allow-trailing-commas=true file.json
biome format --json-parse-allow-trailing-commas=true file.json
biome lint --json-parse-allow-trailing-commas=true file.json
biome ci --json-parse-allow-trailing-commas=true file.json
```
#7758 cea002f Thanks @ematipico! - Promoted new lint rules:
- Promoted noNonNullAssertedOptionalChain to the suspicious group
- Promoted useReactFunctionComponents to the style group
- Promoted useImageSize to the correctness group
- Promoted useConsistentTypeDefinitions to the style group
- Promoted useQwikClasslist to the correctness group
- Promoted noSecrets to the security group
Removed the lint rule useAnchorHref, because its use case is covered by useValidAnchor.

#6356 296627d Thanks @wrick17! - Added the new checkstyle reporter. When --reporter=checkstyle is passed to the CLI, Biome will emit diagnostics for Checkstyle format:

<?xml version="1.0" encoding="utf-8"?>
<checkstyle version="4.3">
  <file name="index.ts">
    <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" />
    <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" />
    <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" />
    <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" />
    <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" />
    <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" />
  </file>
  <file name="main.ts">
    <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" />
    <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" />
    <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" />
    <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" />
    <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" />
    <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" />
  </file>
</checkstyle>

#7488 b13e524 Thanks @kpapa05! - Added "@rbxts/react" as an alias for "react" for handling the reactClassic jsxRuntime.
#7536 0bccd34 Thanks @TheAlexLichter! - Added .oxlintrc.json to well-known files.
#7548 85d3a3a Thanks @siketyan! - The following rules are now a part of the react domain, and they won't be enabled automatically unless you enabled the domain, or Biome detects react as a dependency of your closest package.json:
- lint/correctness/noChildrenProp (recommended)
- lint/correctness/noReactPropAssignments
- lint/security/noDangerouslySetInnerHtml (recommended)
- lint/security/noDangerouslySetInnerHtmlWithChildren (recommended)
- lint/style/useComponentExportOnlyModules
- lint/suspicious/noArrayIndexKey (recommended)
#7667 480909a Thanks @ematipico! - Added the ability to show severity Information diagnostics in reporter outputs.

If one or more rules are triggered, and they are configured to emit an Information diagnostic, now they're counted in the final output:
```
Checked 1 file in <TIME>. No fixes applied.
Found 1 info.
```
#7702 28e8860 Thanks @ematipico! - Added linting and assist support for .html files, with addition of two new configurations:
- html.linter.enabled
- html.assist.enabled
The HTML linter, in this release, only contains the rule noHeaderScope. More rules will be released in the upcoming releases.
#7164 f66b0c5 Thanks @dyc3! - Added a new CSS parser option tailwindDirectives. Enabling this option will allow all of Tailwind v4's syntax additions to be parsed and formatted by Biome.

You can enable this by setting css.parser.tailwindDirectives to true in your Biome configuration.
```
{
  "css": {
    "parser": {
      "tailwindDirectives": true
    }
  }
}
```
#7669 6ed4d16 Thanks @barklund! - React 19.2 support is now supported in Biome:
- Treats useEffectEvent like useRef in useExhaustiveDependencies
- Added <Activity /> to known React APIs.
#7702 28e8860 Thanks @ematipico! - Added experimental full support for HTML, Vue, Svelte and Astro files. In this release, the HTML parser
has been enhanced, and it's now able to parse .vue, .svelte and .astro files.

This means that now Biome is able to lint and format the JavaScript (TypeScript), HTML and CSS code that is contained in these files.

Now that the main architecture is stable and working, in the upcoming patches and minors we will also fix possible inaccuracies and edge cases coming from existing lint rules, such as noUnusedVariables inside <script> blocks or frontmatter.

The support is considered experimental because there might be cases that aren't fine-parsed yet, hence causing possible inaccuracies when it comes to formatting and linting.
#7599 09445c8 Thanks @anaisbetts! - #### lineEnding has a new option auto

The option lineEnding now has a variant called auto to match the operating system's expected
line-ending style: on Windows, this will be CRLF (\r\n), and on macOS / Linux, this will
be LF (\n).

This allows for cross-platform projects that use Biome not to have to
force one option or the other, which aligns better with Git's default behavior
on these platforms.

Example usage:
```
{
  "formatter": {
    "lineEnding": "auto"
  }
}
```
```
biome format --line-ending auto
```
#7392 e4feb8e Thanks @ematipico! - Added new capabilities to the CLI arguments --skip and --only, available to the biome lint command.

--skip and --only can now accept domain names; when provided, Biome will run or skip all the rules that belong to a certain domain.

For example, the following command will only run the rules that belong to the next domain:
```
biome lint --only=next
```
Another example, the following command will skip the rules that belong to the project domain:
```
biome lint --skip=project
```
#7702 28e8860 Thanks @ematipico! - Added a new option called html.interpolation. This option enables the parsing of text expressions (or interpolation) in HTML files.

The following file.html will be correctly formatted:
```

<div>
  Hello {{ name }}!
  <p>Your balance is: {{ account.balance }}</p>
  <button>{{ isLoading ? "Loading..." : "Submit" }}</button>
</div>
```
To note that html.interpolation only parses text expressions that are delimited by double curly braces ({{ }}). The content of expressions is parsed as normal text.

Patch Changes

#7712 fcc9b42 Thanks @minht11! - Added new rule useVueDefineMacrosOrder which allows enforcing specific order for Vue compiler macros.

In this example, the rule will suggest moving defineProps before defineEmits:
```
<script lang="ts" setup>
const emit = defineEmits(["update"]);
const props = defineProps<{ name: string }>();
</script>
```
#7698 3b6f5e3 Thanks @ematipico! - Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.
#7819 ef45056 Thanks @ematipico! - Fixed #7788. Removes some error logging that were emitted when loading possible configuration files.
#7593 e51dd55 Thanks @arendjr! - Fixed an issue with the files.maxSize setting. Previously the setting would always be looked up in the root settings, even in monorepos where a closer biome.json is available. It now correctly uses the nearest configuration.
#7825 ad55b35 Thanks @Conaclos! - Fixed #7798. useNamingConvention no longer panics when it encounters a name that consists of a single dollar sign $ that doesn't match a custom convention.
#7764 93be2ab Thanks @gaauwe! - Fixed #6589: Biome now properly loads extension settings before loading the configuration file when opening a text document in the LSP server.

`v2.2.7`

Compare Source

Patch Changes

#7715 b622425 Thanks @Netail! - Added the nursery rule noEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter.
#7714 c7e5a14 Thanks @MeGaNeKoS! - Increased the maximum line limit for noExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components.
#5868 2db73ae Thanks @bushuai! - Fixed #5856, noRedundantUseStrict now keeps leading trivia
#7756 d665c97 Thanks @ematipico! - Improved the diagnostic message of the rule noDuplicateTestHooks.

`v2.2.6`

Compare Source

Patch Changes

#7071 a8e7301 Thanks @ptkagori! - Added the useQwikMethodUsage lint rule for the Qwik domain.

This rule validates Qwik hook usage. Identifiers matching useXxx must be called only within serialisable reactive contexts (for example, inside component$, route loaders/actions, or within other Qwik hooks), preventing common Qwik antipatterns.

Invalid:

// Top-level hook call is invalid.
const state = useStore({ count: 0 });

function helper() {
  // Calling a hook in a non-reactive function is invalid.
  const loc = useLocation();
}

Valid:

component$(() => {
  const state = useStore({ count: 0 }); // OK inside component$.
  return <div>{state.count}</div>;
});

const handler = $(() => {
  const loc = useLocation(); // OK inside a $-wrapped closure.
  console.log(loc.params);
});

#7685 52071f5 Thanks @denbezrukov! - Fixed #6981: The NoUnknownPseudoClass rule no longer reports local pseudo-classes when CSS Modules are used.
#7640 899f7b2 Thanks @arendjr! - Fixed #7638: useImportExtensions no longer emits diagnostics on valid import paths that end with a query or hash.

Example

// This no longer warns if `index.css` exists:
import style from "../theme/index.css?inline";

#7071 a8e7301 Thanks @ptkagori! - Added the useQwikValidLexicalScope rule to the Qwik domain.

This rule helps you avoid common bugs in Qwik components by checking that your variables and functions are declared in the correct place.

Invalid:

// Invalid: state defined outside the component's lexical scope.
let state = useStore({ count: 0 });
const Component = component$(() => {
  return (
    <button onClick$={() => state.count++}>Invalid: {state.count}</button>
  );
});

Valid:

// Valid: state initialised within the component's lexical scope and captured by the event.
const Component = component$(() => {
  const state = useStore({ count: 0 });
  return <button onClick$={() => state.count++}>Valid: {state.count}</button>;
});

#7620 5beb1ee Thanks @Netail! - Added the rule useDeprecatedDate, which makes a deprecation date required for the graphql @deprecated directive.

Invalid

query {
  member @&#8203;deprecated(reason: "Use `members` instead") {
    id
  }
}

Valid

query {
  member
    @&#8203;deprecated(reason: "Use `members` instead", deletionDate: "2099-12-25") {
    id
  }
}

#7709 d6da4d5 Thanks @siketyan! - Fixed #7704: The useExhaustiveDependencies rule now correctly adds an object dependency when its method is called within the closure.

For example:
```
function Component(props) {
  useEffect(() => {
    props.foo();
  }, []);
}
```
will now be fixed to:
```
function Component(props) {
  useEffect(() => {
    props.foo();
  }, [props]);
}
```
#7624 309ae41 Thanks @lucasweng! - Fixed #7595: noUselessEscapeInString no longer reports $\{ escape in template literals.
#7665 29e4229 Thanks @ryan-m-walker! - Fixed #7619: Added support for parsing the CSS :state() pseudo-class.
```
custom-selector:state(checked) {
}
```
#7608 41df59b Thanks @ritoban23! - Fixed #7604: the useMaxParams rule now highlights parameter lists instead of entire function bodies. This provides more precise error highlighting. Previously, the entire function was highlighted; now only the parameter list is highlighted, such as (a, b, c, d, e, f, g, h).
#7643 459a6ac Thanks @daivinhtran! - Fixed #7580: Include plugin in summary report

`v2.2.5`

Compare Source

Patch Changes

#7597 5c3d542 Thanks @arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.
#7269 f18dac1 Thanks @CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.
```
// Ended up as: - const t = "Text"
const t = <>Text</>

// Ended up as: - const e = t ? "Option A" : "Option B"
const e = t ? <>Option A</> : <>Option B</>

/* Ended up as:
  function
```

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone 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 was generated by Mend Renovate. View the repository job log.

cloudflare-workers-and-pages · 2025-08-04T00:33:13Z

Deploying sit-frontend with Cloudflare Pages

Latest commit:	`01a28ec`
Status:	✅ Deploy successful!
Preview URL:	https://e437f250.sit-frontend.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.sit-frontend.pages.dev

View logs

renovate bot added the t: dependencies label Aug 4, 2025

renovate bot requested a review from derklaro August 4, 2025 00:32

renovate bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from 8b58468 to d88c0d7 Compare August 11, 2025 20:50

renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 9ead9d7 to d567b44 Compare August 16, 2025 00:50

renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 89f5769 to 3ed1f73 Compare October 20, 2025 15:12

renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 715b9e1 to 6e6bd7f Compare October 27, 2025 15:44

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 7e05327 to b5883bc Compare October 28, 2025 16:36

chore: update all non-major dependencies

01a28ec

renovate bot force-pushed the renovate/all-minor-patch branch from b5883bc to 01a28ec Compare October 29, 2025 00:00

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore: update all non-major dependencies #33

chore: update all non-major dependencies #33

Uh oh!

renovate bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages bot commented Aug 4, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

chore: update all non-major dependencies #33

Are you sure you want to change the base?

chore: update all non-major dependencies #33

Uh oh!

Conversation

renovate bot commented Aug 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.3.2

Patch Changes

v2.3.1

Patch Changes

v2.3.0

Minor Changes

Example

Example

Example

Patch Changes

v2.2.7

Patch Changes

v2.2.6

Patch Changes

Example

Invalid

Valid

v2.2.5

Patch Changes

Configuration

Uh oh!

cloudflare-workers-and-pages bot commented Aug 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying sit-frontend with Cloudflare Pages

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Aug 4, 2025 •

edited

Loading

`v2.3.2`

`v2.3.1`

`v2.3.0`

`v2.2.7`

`v2.2.6`

`v2.2.5`

cloudflare-workers-and-pages bot commented Aug 4, 2025 •

edited

Loading