Skip to content

fix(deps): update all non-major dependencies - #51

Open
renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate-appwrite

@renovate-appwrite renovate-appwrite Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@biomejs/biome (source) 2.2.4 → 2.6.7 age confidence
@lobehub/icons 5.0.1 → 5.23.1 age confidence
@openrouter/sdk ^0.9.11 → ^0.13.0 age confidence
@plausible-analytics/tracker (source) 0.4.4 → 0.4.7 age confidence
@tailwindcss/vite (source) 4.2.1 → 4.3.5 age confidence
@tanstack/devtools-vite (source) 0.8.5 → 0.8.6 age confidence
@tanstack/react-devtools (source) 0.10.13 → 0.10.14 age confidence
@tanstack/react-query (source) 5.104.0 → 5.107.1 age confidence
@tanstack/react-router (source) 1.170.41 → 1.170.46 age confidence
@tanstack/react-router-devtools (source) 1.167.2 → 1.167.3 age confidence
@tanstack/react-start (source) 1.168.60 → 1.169.5 age confidence
@tanstack/router-plugin (source) 1.168.42 → 1.169.0 age confidence
@testing-library/dom 10.4.1 → 10.4.2 age confidence
@testing-library/react 16.3.2 → 16.3.3 age confidence
@types/bun (source) 1.4.2 → 1.4.4 age confidence
@types/node (source) 22.19.13 → 22.20.5 age confidence
@types/react (source) 19.2.14 → 19.3.0 age confidence
@types/react-dom (source) 19.2.3 → 19.3.0 age confidence
@vitejs/plugin-react (source) 5.1.4 → 5.2.0 age confidence
lucide-react (source) ^0.545.0 → ^0.577.0 age confidence
react (source) 19.2.4 → 19.3.1 age confidence
react-dom (source) 19.2.4 → 19.3.1 age confidence
recharts 3.7.0 → 3.10.1 age confidence
tailwindcss (source) 4.2.1 → 4.3.5 age confidence
vite (source) 7.3.7 → 7.3.8 age confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v2.6.7

Compare Source

Patch Changes
  • #​12906 b3375d2 Thanks @​dyc3! - Added the nursery rule noAsyncPromiseFinally, which reports async functions passed to a promise's .finally() method. If such a function fails, its error replaces the original result or error of the promise.

    promise.finally(async () => {
        await cleanup();
    });
  • #​12894 e24da6f Thanks @​dyc3! - Added the nursery rule noDuplicateTypeConstituents, which reports types listed more than once in a union or intersection type, and undefined in the type of an optional parameter.

    type T = string | number | string;
    function f(a?: string | undefined) {}
  • #​12899 6c15027 Thanks @​dyc3! - Added the nursery rule noExcessiveSelectorComplexity, which limits how many IDs, type selectors, attribute selectors, pseudo-classes, universal selectors, compound selectors, and combinators a CSS selector can contain. It can also disallow chosen combinators, pseudo-classes, pseudo-elements, attributes, and attribute operators. The rule does nothing until an option is set.

    For example, with "maxIds": 1, the following selector is reported:

    #main #sidebar {}
  • #​12897 0b8f429 Thanks @​dyc3! - Added the new nursery rule noInvalidFetchOptions, which reports a body in the options of fetch() and new Request() when the method is GET or HEAD. These calls throw a TypeError at runtime. When no method is given, the request uses GET.

    await fetch("/", { method: "GET", body: "foo=bar" });
  • #​12926 9b6b9f4 Thanks @​dyc3! - Added the nursery rule noNewArray, which reports new Array() calls with a single argument. Such a call creates an empty array of the given length when the argument is a number, and an array that holds the argument otherwise.

    const array = new Array(length);
  • #​12895 739440f Thanks @​dyc3! - Added the new nursery rule noRedundantTypeConstituents, which reports members of union and intersection types that have no effect, such as a literal type next to its primitive type, or never in a union.

    type Status = "active" | string;
  • #​12810 71ab61b Thanks @​dyc3! - Added the nursery rule noSvelteAsyncStore, which disallows passing async functions to the writable(), readable(), and derived() stores from svelte/store.

    import { writable } from "svelte/store";
    const user = writable(null, async (set) => {
        set(await fetchUser());
    });
  • #​12917 37d9f41 Thanks @​dyc3! - Added the new nursery rule noUnresolvedDefaultImport, which reports default imports from modules that have no default export. The rule is part of the project domain.

    // foo.js only contains `export function foo() {}`
    import foo from "./foo.js";
  • #​12892 f16842e Thanks @​dyc3! - Added the nursery rule noUselessFallbackInSpread, which reports empty object fallbacks when spreading a value into an object. Spreading null, undefined, or another falsy value into an object adds no properties, so the fallback has no effect.

    const object = { ...(options || {}) };
  • #​12785 c198be2 Thanks @​dyc3! - Added the new nursery rule noUselessParameterPropertyAssignment, which reports constructor assignments such as this.name = name when name is a parameter property. TypeScript already sets the property to the parameter's value, so the assignment does nothing.

    class User {
      constructor(public name: string) {
        this.name = name;
      }
    }
  • #​12900 a4d1b0f Thanks @​dyc3! - Added the nursery rule noUselessSpread, which reports spread syntax that has no effect. For example, [first, ...[second]] can be written as [first, second], and new Set([...items]) can be written as new Set(items).

  • #​12902 d7d755b Thanks @​dyc3! - Added the nursery rule noVueExposeAfterAwait, which reports expose() and defineExpose() calls that come after an await in a Vue component's setup code. These calls run too late, so a parent component might not receive the exposed properties.

    <script setup>
    await fetchUser();
    defineExpose({ reload });
    </script>
  • #​12596 d33e56e Thanks @​dyc3! - Added the nursery rule useAtomicUpdates, which reports assignments in async functions and generators that can be based on an outdated value because the function paused at an await or yield after reading it.

    let total = 0;
    async function addToTotal(getAmount) {
        total += await getAmount(); // reported
    }
  • #​12901 48e3572 Thanks @​dyc3! - Added the new nursery rule useConsistentBooleanName. It requires variables, parameters, and functions that hold or return a boolean to start with a prefix such as is or has, and reports names with those prefixes that don't hold or return a boolean.

    const completed = progress === 100;
    const hasName = "Sindre";
  • #​12905 5b00387 Thanks @​dyc3! - Added the nursery rule useConsistentFontWeightNotation, which enforces writing font weights either as numbers or as the keywords normal and bold where possible. It checks the font-weight and font properties, and its safe fix converts between normal/bold and 400/700.

    a { font-weight: bold; }
  • #​12922 8d33c85 Thanks @​dyc3! - Added the nursery rule useConsistentTupleLabels, which reports tuple type elements without a label when other elements of the same tuple have one.

    type Point = [x: number, number];
  • #​12925 7252cbd Thanks @​dyc3! - Added the new nursery rule useGlobalRegexInMatchAll, which reports calls to matchAll() with a regular expression that doesn't have the g flag. These calls throw a TypeError at runtime.

    text.matchAll(/pattern/);
  • #​12891 e781bc3 Thanks @​dyc3! - Added the nursery rule useGlobalRegexInReplaceAll, which reports regular expressions without the g flag passed to replaceAll(). These calls throw a TypeError instead of replacing text.

    withSpaces.replaceAll(/\s+/, ",");
  • #​12896 a968e1a Thanks @​dyc3! - Added the new nursery rule useValidCharacterComparison, which reports comparisons between a single character and a string that has more than one character. Such comparisons are always false, or always true with !== and !=.

    text.charAt(0) === "ab";
  • #​13085 7a795d0 Thanks @​ematipico! - Fixed withastro/compiler-rs#221 so Astro template expressions containing comment-only JSX expression children, such as <span>{<!-- x -->}</span>, parse without diagnostics.

  • #​12621 79ce388 Thanks @​latin-1! - Fixed #​12413 and #​12414: useSortedProperties now sorts consecutive groups of properties independently, preserving the positions of nested rules, at-rules, and SCSS variable declarations.

  • #​13065 bd9faae Thanks @​ematipico! - Fixed #​5848: running useSortedKeys or useSortedSelectionSet as an editor source action no longer corrupts nested objects or selection sets.

  • #​13056 98f4d53 Thanks @​ematipico! - Fixed #​10607: noUndeclaredDependencies no longer reports imports resolved through TypeScript's compilerOptions.paths mappings.

  • #​13033 7638393 Thanks @​GBra-4-669! - Fixed #​12980: the CSS parser no longer panics on a composes declaration whose value contains a non-identifier token, such as composes: 1px;. It reports a diagnostic instead.

  • #​12917 37d9f41 Thanks @​dyc3! - Fixed noUnresolvedImports: it now reports default imports from modules that only forward exports with export * from "...". export * never re-exports a default export, so import foo from "./barrel.js" fails when ./barrel.js contains only export * from "./foo.js".

  • #​12596 d33e56e Thanks @​dyc3! - Fixed noUnreachableSuper ignoring the default values of constructor parameters. Using this in a default value is now reported, because it runs before super(), and calling super() in a default value is now recognized.

    class Child extends Parent {
    	constructor(options = this.defaults()) { // reported
    		super(options);
    	}
    }
  • #​12596 d33e56e Thanks @​dyc3! - Fixed noUselessAssignment ignoring variables that are used in the iterated value of a for...of or for...in loop, in the default values of a destructuring declaration or of parameters, or in the body of an arrow function written as a single expression. These variables are now checked too.

    function process(first, second) {
    	let list = first; // reported: this value is never read
    	list = second;
    	for (const item of list) {
    		handle(item);
    	}
    }
  • #​12805 2468384 Thanks @​vibbix! - Fixed #​12332: noUnknownUnit no longer reports hex colors that start with a digit in SCSS custom properties or in unquoted legacy IE filter values. The rule now accepts --accent: #&#8203;4566a8; instead of reporting the unknown unit a8.

  • #​12549 7fdb28f Thanks @​pkallos! - Fixed #​10464: useNullishCoalescing no longer reports a ternary or if statement that checks only null or only undefined when the type can also be the other, because ?? would change its behavior.

  • #​12952 d1896a0 Thanks @​arendjr! - Added grit() queries to JavaScript plugins. A rule can now use a GritQL pattern to select the nodes passed to run() instead of listing syntax kinds with ast().

    For example:

    export const noConsole = defineRule({
      query: grit("`console.log($args)`"),
      run(element) {
        if (element.kind !== "JS_CALL_EXPRESSION") return;
        registerDiagnostic(element, "warning", "Unexpected console.log.");
      },
    });

    Usage of Grit patterns can be particularly useful when it would take several checks to verify the shape of a snippet that involves multiple AST nodes.

    Grit sequence patterns call run() for each matched node. Matching on leaf tokens is also supported for patterns, while patterns containing rewrites are rejected. Plugins using GritQL patterns should report diagnostics from run() as usual.

    Plugins using Grit queries can still request the semantic model as well:

    export const rule = defineRule({
      query: grit("function $fn($args) { $body }", { semantic: true }),
      run(node, { model }) {
        // You can use `model` here similar to a query specified using `ast(..., { semantic: true })`.
      },
    });
  • #​13022 81d0187 Thanks @​arendjr! - Fixed an issue where GritQL patterns wouldn't match snippets if they contain a trailing list separator.

    For example, the pattern `a, b` wouldn't match the arguments in function(a, b,), whereas now they do.

  • #​12999 ace98cf Thanks @​deepsingh132! - Fixed #​12953: the Markdown formatter no longer removes the blank line between a blockquote that ends a list item and the block that follows it, matching Prettier. Removing that line could also move a following paragraph into the blockquote. The same applies to a list item that ends with a hard line break.

     - a
       > b
    +
     #### Heading
  • #​13067 45c8c4d Thanks @​ematipico! - Added the nursery rule noDisabledAttribute, which warns when buttons and other form controls use the native disabled attribute. A disabled control can't be reached with the Tab key, so the rule suggests aria-disabled or readonly instead.

    <button disabled>Save</button>
    <input type="email" disabled />
  • #​12923 0668c8f Thanks @​dyc3! - Added the new nursery rule noScssNullComparison. It reports comparisons to null in Sass @if and @else if conditions, because null already counts as false in a condition.

    a {
      @if $value == null {}
    }
  • #​12955 e1ef913 Thanks @​ematipico! - Fixed an issue where Biome could silently skip configured plugins. Biome now reports an error when those plugins are unavailable during analysis.

  • #​12997 419aa5d Thanks @​Riccardo-bit-cpu! - Fixed #​12475: noSwitchDeclarations no longer reports var declarations inside switch clauses, matching ESLint's no-case-declarations.

  • #​12867 6a25d72 Thanks @​dyc3! - Added the nursery rule noUselessQualifier, which reports namespace and enum names that are repeated before a member inside that same namespace or enum. Biome provides a fix that removes the repeated name.

    namespace Shapes {
      export type Point = { x: number; y: number };
      const origin: Shapes.Point = { x: 0, y: 0 };
    }
  • #​12050 60f4695 Thanks @​dor-sr! - Fixed #​11933: useUnicodeRegex no longer offers to add the u flag to patterns that become invalid or change meaning in Unicode mode, such as /{/, /\-/ or /[\d-z]/. The rule still reports them.

  • #​13035 478e056 Thanks @​dyc3! - Fixed #​13026: the Markdown formatter no longer indents the rows of a table inside a blockquote when the table follows a paragraph of two or more lines. Previously, every run of the formatter indented the rows further until they were joined onto the header line.

      > First line of a paragraph,
      > second line of it.
      >
      > | A   | B   |
    -   > | --- | --- |
    -   > | x   | y   |
    + > | --- | --- |
    + > | x   | y   |
  • #​13066 f6cf28e Thanks @​arendjr! - Removed the semantic() query function from the JavaScript plugin API. Pass { semantic: true } to ast() instead to provide the semantic model to a rule.

    export const rule = defineRule({
      query: semantic("JS_REFERENCE_IDENTIFIER"),
      run(node, { model }) {
        // Use `model` here.
      },
    });

    Becomes:

    export const rule = defineRule({
      query: ast("JS_REFERENCE_IDENTIFIER", { semantic: true }),
      run(node, { model }) {
        // Use `model` here.
      },
    });

    This behaviour matches the grit() query function, which also accepts the { semantic: true } option.

  • #​12951 014b976 Thanks @​ematipico! - Fixed #​10782: noUndeclaredClasses no longer appears to hang on projects with long component import chains.

  • #​13073 827e610 Thanks @​vibbix! - Fixed #​13072: a comment before a SCSS map entry whose value is a parenthesized group no longer indents that group one level too deep. This matches Prettier 3.10 behavior now.

      $map: (
        /* comment */
        key: (
    -       a: 1,
    -       b: 2,
    -     ),
    +     a: 1,
    +     b: 2,
    +   ),
      );
  • #​12928 ae0e186 Thanks @​dyc3! - Improved noUselessStringConcat. The rule now reports literals joined after another value, such as foo + "a" + "b", and fixes template literals with placeholders, so `Hello, ${name}` + "!" becomes `Hello, ${name}!`.

    The rule no longer reports strings that would join into text that looks like a placeholder, such as "$" + "{name}", or into a directive such as "use strict". It also no longer reports obj.foo * "a" + "b", which its fix used to change to obj.foo * "ab".

    The fix no longer changes the value of the string in two cases. It used to change 1 + 2 + "b" + "c" to "12bc" instead of 1 + 2 + "bc". It used to change "\1" + "2" to "\12", which is a different escape sequence.

    The fix no longer joins literals that are on different lines when the concatenation ends with two literals on the same line. It also no longer puts a line break from a template literal into a string literal, which made the code invalid.

  • #​13048 24734a8 Thanks @​ematipico! - Fixed #​13028: Biome now keeps a paragraph in its outer block quote when a quote-only blank line closes a nested block quote.

     > > b
     >
    -> > c
    +> c
  • #​12967 bd0988e Thanks @​siketyan! - Fixed #​12827: noDuplicateProperties, noDuplicateCustomProperties, and noMissingVarFunction now check declarations at the top level of embedded CSS templates, such as styled.div`...`.

  • #​13048 24734a8 Thanks @​ematipico! - Fixed #​13029: the Markdown formatter now normalizes spaces inside inline and reference link text without removing whitespace-only text.

    -something [ text   ](   destination)
    -something [    ](   destination)
    +something [ text ](destination)
    +something [ ](destination)
  • #​13021 05a1409 Thanks @​dyc3! - Fixed #​12993: Svelte {@const} tags with TypeScript type annotations, such as {@const doubled: number = item * 2}, now parse and format in components with <script lang="ts">.

  • #​12968 ec0142b Thanks @​siketyan! - Fixed #​12826: Biome now detects CSS in styled-components templates that use .attrs(), such as styled.button.attrs({ type: "button" })`...` and styled(Component).attrs(() => ({}))`...`, so they are formatted and linted like styled.button`...`.

  • #​13048 24734a8 Thanks @​ematipico! - Fixed #​13027: the Markdown formatter now preserves spaces around text after a code span that crosses block quote lines.

     > `a
    -> b`c`d`
    +> b` c `d`
  • #​13055 78c744a Thanks @​ematipico! - Fixed #​13053: Biome now reports missing CLI paths as file-system errors without the INTERNAL tag or advice that the path was ignored by configuration. File-system diagnostics now use specific fs/* categories, with underlying I/O errors categorized as fs/io.

  • #​12927 c6feec1 Thanks @​dyc3! - Added the nursery rule useCatchErrorName, which requires a specific name for caught errors in try...catch statements and in the error handlers of promise.catch() and promise.then(). The name defaults to error and can be changed with the name option.

    try {} catch (err) {} // `err` should be named `error`
  • #​12788 7f971ed Thanks @​dyc3! - Extended useWhile to report for (;;) loops and to fix them to while (true).

  • #​12967 bd0988e Thanks @​siketyan! - Fixed noMissingVarFunction so it also checks declarations inside at-rules such as @page and @font-face. For example, @page { margin: --page-margin; } is now reported when --page-margin is declared in :root.

  • #​13057 d9267a5 Thanks @​ematipico! - Fixed #​10896 so Svelte <script generics> attributes containing object type constraints parse and format as TypeScript type parameters.

  • #​13048 24734a8 Thanks @​ematipico! - Fixed #​13038: Biome now aligns wrapped task-list paragraphs with the text following the checkbox.

     - [ ] Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc varius
    -  malesuada eros, faucibus dapibus odio rhoncus in.
    +      malesuada eros, faucibus dapibus odio rhoncus in.

v2.6.6

Compare Source

Patch Changes
  • #​12887 da0422e Thanks @​dyc3! - Added the new nursery rule noArrayMethodsOnArguments. It reports calls to array methods on the arguments object, which isn't an array, so these calls throw a TypeError when the code runs.

    function sum() {
      return arguments.reduce((total, value) => total + value, 0);
    }
  • #​12877 cd9e10f Thanks @​dyc3! - Added the nursery rule noConstantComparisons, which reports && and || conditions that can never be true, are always true, or contain a check with no effect.

    if (statusCode <= 400 && statusCode > 500) {}
  • #​12876 a7c9586 Thanks @​dyc3! - Added the nursery rule noErasingOperation, which disallows operations with 0 that always result in zero: multiplying by 0, a bitwise AND with 0, and dividing 0 by a number. The other value in these operations has no effect on the result, which usually means the code has a mistake.

    const total = price * 0;
  • #​12841 e954f55 Thanks @​dyc3! - Added the nursery rule noNegatedArrayPredicate, which reports negated calls to Array#some() and Array#every() and suggests moving the negation into the callback function.

    // Invalid: use `array.every((item) => !isUnicorn(item))` instead.
    const isMissing = !array.some((item) => isUnicorn(item));
  • #​12888 15039f7 Thanks @​dyc3! - Added the new nursery rule noNumberArgumentOutOfRange, which reports number literal arguments of toString(), toFixed(), toExponential() and toPrecision() that are outside the range the method accepts. These calls throw a RangeError at runtime.

    value.toString(64);
  • #​12889 1cd7520 Thanks @​dyc3! - Added the nursery rule noSharedBranchCode, which reports code that is repeated at the start or end of every branch of an if statement. That code runs no matter which branch is taken, so it can be moved before or after the if statement.

    if (condition) {
      doSomething();
      cleanup();
    } else {
      doSomethingElse();
      cleanup();
    }
  • #​12842 [d47fcfd](https://redirect.github.com/biomejs/biome/com

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Monday (* * * * 1)
  • 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 CLI.

@renovate-appwrite

renovate-appwrite Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @emoji-mart/react@1.1.1
npm warn Found: react@19.3.1
npm warn node_modules/react
npm warn   react@"^19.2.0" from the root project
npm warn   132 more (@ant-design/cssinjs, @ant-design/cssinjs-utils, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"^16.8 || ^17 || ^18" from @emoji-mart/react@1.1.1
npm warn node_modules/@emoji-mart/react
npm warn   @emoji-mart/react@"^1.1.1" from @lobehub/ui@5.64.4
npm warn   node_modules/@lobehub/ui
npm warn
npm warn Conflicting peer dependency: react@18.3.1
npm warn node_modules/react
npm warn   peer react@"^16.8 || ^17 || ^18" from @emoji-mart/react@1.1.1
npm warn   node_modules/@emoji-mart/react
npm warn     @emoji-mart/react@"^1.1.1" from @lobehub/ui@5.64.4
npm warn     node_modules/@lobehub/ui
npm warn ERESOLVE overriding peer dependency
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @tanstack/react-start@1.169.5
npm error Found: vite@7.3.8
npm error node_modules/vite
npm error   peerOptional vite@">=8.0.0" from @tanstack/start-plugin-core@1.171.56
npm error   node_modules/@tanstack/react-start/node_modules/@tanstack/start-plugin-core
npm error     @tanstack/start-plugin-core@"1.171.56" from @tanstack/react-start@1.169.5
npm error     node_modules/@tanstack/react-start
npm error       @tanstack/react-start@"^1.168.60" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vite@">=8.0.0" from @tanstack/react-start@1.169.5
npm error node_modules/@tanstack/react-start
npm error   @tanstack/react-start@"^1.168.60" from the root project
npm error
npm error Conflicting peer dependency: vite@8.3.8
npm error node_modules/vite
npm error   peerOptional vite@">=8.0.0" from @tanstack/react-start@1.169.5
npm error   node_modules/@tanstack/react-start
npm error     @tanstack/react-start@"^1.168.60" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-11-22T14_27_42_712Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-11-22T14_27_42_712Z-debug-0.log

@appwrite

appwrite Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Code review

Commit Status Tier Verdict Details
0addf58 Reviewed Reviewed 🟡 B · Needs changes before merging 💬 Commented View review

Several earlier findings remain open for lockfile synchronization, SDK API compatibility, TanStack Start/Vite compatibility, and Recharts types.

This update bumps the benchmark OpenRouter SDK to 0.13 and refreshes its npm lockfile. It also updates root dependencies and the corresponding pnpm resolution.

1 of 4 changed files was too large to include in full.

Fix with agent prompt
### Issue 1
package.json:29
**Keep the root npm lockfile in sync**

The tracked root `package-lock.json` still declares `lucide-react` as `^0.545.0` and Biome as `2.2.4`, so a clean `npm ci` rejects the updated manifest as out of sync. The pnpm lockfile is refreshed, but the README documents npm for development; please refresh the npm lockfile as well.

### Issue 2
benchmark/package.json:20
**Update the benchmark Bun lockfile too**

`benchmark/bun.lock` still declares `@openrouter/sdk` as `^0.9.11` and resolves 0.9.11, while the benchmark manifest now requests `^0.13.0`. Since the benchmark scripts use Bun, a frozen Bun install cannot use the updated dependency until this lockfile is refreshed.

### Issue 3
benchmark/package-lock.json:17-19
**SDK upgrade breaks the benchmark's chat request calls**

With SDK 0.13.67, `chat.send` expects `chatRequest`, but `benchmark/src/runner.ts:107` and `benchmark/src/judge.ts:34` still pass `chatGenerationParams`. Running `cd benchmark && npx tsc --noEmit` now fails at both calls, so the benchmark cannot be built until they use the new request shape.

### Issue 4
pnpm-lock.yaml:2116
**TanStack Start 1.169.4 requires Vite 8**

This resolution changes React Start's Vite peer requirement from `>=7` in 1.168.60 to `>=8`, but the app still locks Vite 7.3.7. The production build (`npx --yes pnpm@10.10.0 build`) now fails with `Could not resolve entry module "index.html"`; please keep a Vite-7-compatible Start release or upgrade Vite as part of this change.

### Issue 5
pnpm-lock.yaml:3744
**Recharts 3.10.1 breaks existing chart prop types**

After `npx --yes pnpm@10.10.0 install --frozen-lockfile`, `npx --yes pnpm@10.10.0 exec tsc --noEmit` reports errors at `src/components/charts/RadarPerformance.tsx:144,172` and `src/components/charts/SkillsComparisonChart.tsx:89,92`: the `Legend` payload/click props and custom `Bar` shape/radius no longer match Recharts' types. The chart code therefore no longer type-checks with this lockfile resolution.

### Issue 6
pnpm-lock.yaml:2116
**Start 1.169.5 breaks server-function input typing**

The same `tsc --noEmit` run fails at `src/lib/leaderboard-summary.ts:45,51` because `createServerFn().handler(...)` now has no declared `data` input, and at `src/routes/api/summary.$mode.ts:9` because the call passes a string where the generated function expects `undefined`. The summary endpoint's server-function contract needs to be updated for this Start version or kept on a compatible release.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Walkthrough (4)
File Change
package.json Bumps root Lucide React and Biome dependency ranges.
benchmark/package.json Bumps the benchmark OpenRouter SDK range to 0.13.
benchmark/package-lock.json Refreshes the benchmark npm resolution to SDK 0.13.67.
pnpm-lock.yaml Refreshes the resolved dependency set for the root project.
Still open from earlier reviews (6)

Reviewed 0addf58

Tip

Comment @appwrite review to re-run, or mention @appwrite with a question.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Tier A · See the inline comments. Summary

Comment thread package.json
"@tanstack/router-plugin": "^1.168.42",
"@types/bun": "^1.3.10",
"lucide-react": "^0.545.0",
"lucide-react": "^0.577.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep the root npm lockfile in sync

The tracked root package-lock.json still declares lucide-react as ^0.545.0 and Biome as 2.2.4, so a clean npm ci rejects the updated manifest as out of sync. The pnpm lockfile is refreshed, but the README documents npm for development; please refresh the npm lockfile as well.

Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 29

Comment:
**Keep the root npm lockfile in sync**

The tracked root `package-lock.json` still declares `lucide-react` as `^0.545.0` and Biome as `2.2.4`, so a clean `npm ci` rejects the updated manifest as out of sync. The pnpm lockfile is refreshed, but the README documents npm for development; please refresh the npm lockfile as well.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

Comment thread benchmark/package.json
},
"dependencies": {
"@openrouter/sdk": "^0.9.11"
"@openrouter/sdk": "^0.13.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update the benchmark Bun lockfile too

benchmark/bun.lock still declares @openrouter/sdk as ^0.9.11 and resolves 0.9.11, while the benchmark manifest now requests ^0.13.0. Since the benchmark scripts use Bun, a frozen Bun install cannot use the updated dependency until this lockfile is refreshed.

Prompt To Fix With AI
This is a comment left during a code review.
Path: benchmark/package.json
Line: 20

Comment:
**Update the benchmark Bun lockfile too**

`benchmark/bun.lock` still declares `@openrouter/sdk` as `^0.9.11` and resolves 0.9.11, while the benchmark manifest now requests `^0.13.0`. Since the benchmark scripts use Bun, a frozen Bun install cannot use the updated dependency until this lockfile is refreshed.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch from 812b102 to ede53e7 Compare November 10, 2026 06:42

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 1 blocking finding to address. Summary

Comment on lines +17 to +19
"version": "0.13.67",
"resolved": "https://registry.npmjs.org/@openrouter/sdk/-/sdk-0.13.67.tgz",
"integrity": "sha512-kUVaFYA9Xehq67ndTk98i+tRLfYH/F6xSf/WuC8dsukBzcgBvYQydoeKw4Xe+peXG/wOVtDxukWt5SqzhbloKw==",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SDK upgrade breaks the benchmark's chat request calls

With SDK 0.13.67, chat.send expects chatRequest, but benchmark/src/runner.ts:107 and benchmark/src/judge.ts:34 still pass chatGenerationParams. Running cd benchmark && npx tsc --noEmit now fails at both calls, so the benchmark cannot be built until they use the new request shape.

Prompt To Fix With AI
This is a comment left during a code review.
Path: benchmark/package-lock.json
Line: 17-19

Comment:
**SDK upgrade breaks the benchmark's chat request calls**

With SDK 0.13.67, `chat.send` expects `chatRequest`, but `benchmark/src/runner.ts:107` and `benchmark/src/judge.ts:34` still pass `chatGenerationParams`. Running `cd benchmark && npx tsc --noEmit` now fails at both calls, so the benchmark cannot be built until they use the new request shape.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 6447386 to dcd44d1 Compare November 11, 2026 14:34
Comment thread pnpm-lock.yaml

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 2116 · GitHub does not show this file's diff, so this comment is on the file.

TanStack Start 1.169.4 requires Vite 8

This resolution changes React Start's Vite peer requirement from >=7 in 1.168.60 to >=8, but the app still locks Vite 7.3.7. The production build (npx --yes pnpm@10.10.0 build) now fails with Could not resolve entry module "index.html"; please keep a Vite-7-compatible Start release or upgrade Vite as part of this change.

Prompt To Fix With AI
This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 2116

Comment:
**TanStack Start 1.169.4 requires Vite 8**

This resolution changes React Start's Vite peer requirement from `>=7` in 1.168.60 to `>=8`, but the app still locks Vite 7.3.7. The production build (`npx --yes pnpm@10.10.0 build`) now fails with `Could not resolve entry module "index.html"`; please keep a Vite-7-compatible Start release or upgrade Vite as part of this change.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 1 blocking finding to address. Summary

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from b5700a1 to 01008b2 Compare November 18, 2026 14:28
@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b7b7c99 to ae636f5 Compare November 21, 2026 06:35
Comment thread pnpm-lock.yaml

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 3744 · GitHub does not show this file's diff, so this comment is on the file.

Recharts 3.10.1 breaks existing chart prop types

After npx --yes pnpm@10.10.0 install --frozen-lockfile, npx --yes pnpm@10.10.0 exec tsc --noEmit reports errors at src/components/charts/RadarPerformance.tsx:144,172 and src/components/charts/SkillsComparisonChart.tsx:89,92: the Legend payload/click props and custom Bar shape/radius no longer match Recharts' types. The chart code therefore no longer type-checks with this lockfile resolution.

Prompt To Fix With AI
This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 3744

Comment:
**Recharts 3.10.1 breaks existing chart prop types**

After `npx --yes pnpm@10.10.0 install --frozen-lockfile`, `npx --yes pnpm@10.10.0 exec tsc --noEmit` reports errors at `src/components/charts/RadarPerformance.tsx:144,172` and `src/components/charts/SkillsComparisonChart.tsx:89,92`: the `Legend` payload/click props and custom `Bar` shape/radius no longer match Recharts' types. The chart code therefore no longer type-checks with this lockfile resolution.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

Comment thread pnpm-lock.yaml

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 2116 · GitHub does not show this file's diff, so this comment is on the file.

Start 1.169.5 breaks server-function input typing

The same tsc --noEmit run fails at src/lib/leaderboard-summary.ts:45,51 because createServerFn().handler(...) now has no declared data input, and at src/routes/api/summary.$mode.ts:9 because the call passes a string where the generated function expects undefined. The summary endpoint's server-function contract needs to be updated for this Start version or kept on a compatible release.

Prompt To Fix With AI
This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 2116

Comment:
**Start 1.169.5 breaks server-function input typing**

The same `tsc --noEmit` run fails at `src/lib/leaderboard-summary.ts:45,51` because `createServerFn().handler(...)` now has no declared `data` input, and at `src/routes/api/summary.$mode.ts:9` because the call passes a string where the generated function expects `undefined`. The summary endpoint's server-function contract needs to be updated for this Start version or kept on a compatible release.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 2 blocking findings to address. Summary

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch from ae636f5 to 1d5d9c7 Compare November 21, 2026 14:29
@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch from 1d5d9c7 to 0addf58 Compare November 22, 2026 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants