Skip to content

chore(deps): update npm minor and patch - #310

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/npm-minor-and-patch
Open

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/npm-minor-and-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 15, 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
@effect/tsgo (source) 0.63.0 → 0.67.7 age confidence
@tailwindcss/vite (source) 4.3.3 → 4.3.5 age confidence
@tanstack/react-start (source) 1.169.4 → 1.169.5 age confidence
@tanstack/router-cli (source) 1.167.46 → 1.168.0 age confidence
@vitejs/plugin-react (source) 6.1.2 → 6.3.0 age confidence
es-toolkit (source) ^1.53.1 → ^1.53.2 age confidence
eslint (source) 10.13.0 → 10.14.0 age confidence
eslint-plugin-better-tailwindcss 4.10.0 → 4.11.0 age confidence
eslint-plugin-boundaries (source) 7.3.0 → 7.4.1 age confidence
fumadocs-core 16.17.9 → 16.18.4 age confidence
fumadocs-mdx 15.4.10 → 15.5.3 age confidence
fumadocs-ui 16.17.9 → 16.18.4 age confidence
jscpd (source) 5.4.2 → 5.4.3 age confidence
oxc-parser (source) 0.155.0 → 0.157.0 age confidence
rolldown (source) 1.2.16 → 1.3.2 age confidence
tailwindcss (source) 4.3.3 → 4.3.5 age confidence

Changeset automation covers published runtime dependencies only. If this PR changes built output, add a patch changeset per Bot Pull Requests.


Release Notes

Effect-TS/tsgo (@​effect/tsgo)

v0.67.7

Compare Source

Patch Changes

v0.67.5

Compare Source

Patch Changes
  • 689b96f: Finish the tsrs 0.23.0 bump: refresh Cargo.lock for the new tsrs crate versions, and update the release parity check in repoctl tsrs check to read tsrs's new matrix-based build-windows job (same target, runner and build flags, now written as ${{ matrix.target }}). Rework the Oxlint 002-effect-tsgolint-path.patch so it applies to Oxlint 1.92.0 as well as 1.88–1.91: EFFECT_TSGO_TSGOLINT_PATH is now resolved by a wrapper around upstream's try_find_tsgolint_executable instead of an edit inside it (same behavior).
  • c7f44a4: Update the TypeScript next tag to typescript@next, which ships typescript-go commit a59fafb8e7b5b2efef0568149fea03caad02356a, update the TypeScript beta tag to typescript@beta, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

v0.67.4

Compare Source

Patch Changes

v0.67.3

Compare Source

Patch Changes
  • 1477f2e: Fix preferEffectArray, preferEffectRecord, preferEffectString, promiseInEffectSuccess and anyUnknownInErrorContext skipping everything inside a class extends expression. Their walks stop at type nodes, and the extends clause of a class is an ExpressionWithTypeArguments, which counts as one, so the make of a service class was never checked. The walks now visit the expression of a class extends clause; its type arguments, implements clauses and interface extends clauses are still skipped.

    import { Context, Effect } from "effect"
    
    const xs: ReadonlyArray<number> = [1, 2, 3]
    
    export class Doubled extends Context.Service<Doubled, { readonly all: ReadonlyArray<number> }>()("Doubled", {
      make: Effect.gen(function*() {
        // now reported by preferEffectArray
        return { all: xs.map((n) => n * 2) }
      })
    }) {}

    effectFnOpportunity had the same blind spot when checking whether a function declaration is used before it is declared: a call inside an earlier class extends expression was ignored, so it offered to convert a hoisted function into a const that the class would then read before initialization. That opportunity is no longer offered.

    export class Early extends Context.Service<Early, { readonly value: number }>()("Early", {
      make: makeEarly(1) // runs when the class is defined
    }) {}
    
    // no longer suggested as Effect.fn: the const would not be initialized yet
    function makeEarly(n: number) {
      return Effect.gen(function*() {
        return { value: n }
      })
    }

v0.67.1

Compare Source

Patch Changes
  • 71b16e4: CI: cap the Go build cache saved by the TypeScript validation and release jobs at 2 GB. The cache had grown to about 3.5 GB compressed per TypeScript version, and jobs that restore it were running out of disk. The new repoctl go-cache trim command keeps the most recently used files of go env GOCACHE up to the size limit and removes the rest:

    repoctl go-cache trim --max-size 2GB
  • 3922483: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 042e0fb9574980bd67964165df295e629f834fe3, update the TypeScript beta tag to typescript@beta, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

v0.67.0

Compare Source

Minor Changes
  • 45e777b: Run Oxlint's type-aware rules, including the Effect rules, on tsrs with effect-tsgo --tsrs-lint.

    tsrs 0.21.0 ships its port of tsgolint as tsrs --lint. The Effect-patched tsrs now registers the Effect rules there,
    and --tsrs-lint[=<version|tag>] in front of effect-tsgo oxlint or effect-tsgo vp makes the patched Oxlint run
    them on it instead of the patched tsgolint:

    effect-tsgo --tsrs-lint oxlint --type-aware   # the installed tsrs version when it ships, else the latest
    effect-tsgo --tsrs-lint=latest vp lint        # or a tsrs version or tag

    The packaged tsrs is updated to 0.21.0.

v0.64.1

Compare Source

Patch Changes
  • c369721: Fix repoctl spawning npm/pnpm/corepack on Windows after the Effect 4.1.2 update: the .cmd shims now run as a single shell command line, because the spawner no longer accepts shell together with an argument list. This unblocks the win32 release builds.
tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.3.5

Compare Source

Fixed
  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#​20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#​20658, #​20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#​20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#​20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#​20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#​20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#​20632)

v4.3.4

Compare Source

Added
  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#​20367)
Fixed
  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#​20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#​20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#​20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#​20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#​20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#​20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#​20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#​20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#​20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#​20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#​20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#​20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#​20408)
  • Drop invalid UTF-8 candidates during class detection (#​20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#​20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#​20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#​20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#​20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#​20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#​20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#​20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#​20508)
  • Improve style invalidation performance of group-* and peer-* variants (#​20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#​20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#​20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#​20562)
  • Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#​20563)
  • Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#​20563)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#​20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#​20516)
  • Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#​20561)
  • Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#​20547, #​20572)
  • Underline the correct occurrence of an unsupported data type in --value(…) warnings (#​20554)
  • Canonicalization: prefer an existing candidate when collapsing utilities over another utility with the same default theme value (e.g. text-foreground text-primary → text-primary, not text-card-checked-border) (#​20540)
  • Canonicalization: don't collapse utilities into a utility that uses another theme variable with the same default value (e.g. mt-card mb-card → my-card, not my-4) (#​20574)
  • Ensure @tailwindcss/postcss rewrites relative url(…)s of stylesheets that are inlined before it runs (e.g. @imports in Vite) in optimized builds (#​20576)
  • Drop nested rules that put a combinator after a pseudo-element when using pseudo-element variants (e.g. selection:* on a utility with a nested & > * rule) (#​20575)
  • Don't generate CSS for arbitrary values with unbalanced parentheses or brackets (e.g. w-[calc(1px] or [--x:a[b]) (#​20577)
  • Canonicalization: prevent collapse: true from taking exponentially longer when classes are linked through a utility that sets many properties (e.g. sr-only) (#​20558)
  • Ensure & is substituted inside :-moz-any(…) and :-webkit-any(…) in custom variants (e.g. @custom-variant firefox (:-moz-any(&));) (#​20486)
  • Ensure the standalone macOS binaries have a valid code signature, so macOS 27 no longer kills them at launch (#​20578)
  • Ensure @tailwindcss/turbopack and @tailwindcss/webpack rebuild when the input CSS changes (e.g. next dev with Turbopack no longer serves the CSS of the previous edit) (#​20582)
  • Canonicalization: don't drop a utility that sets a --tw-* variable when an unrelated property has the same value (e.g. link mt-4 no longer becomes mt-4 when link sets margin-top: 16px and --tw-translate-x: 16px) (#​20593)
  • Decode single-digit hexadecimal escapes in theme variable and @utility names as the CSS spec does (e.g. @theme { --color-\0: red; } no longer registers --color-0) (#​20591)
  • Don't treat !important inside strings, comments or url() in declaration values as the important flag (e.g. content: "a !important b") (#​20627)
  • Parse a custom property at the end of the input when it has no trailing ; (e.g. --foo: bar as the last declaration) (#​20653)
  • Keep a declaration without a ; at the end of the CSS input (e.g. color: red) (#​20655)
TanStack/router (@​tanstack/react-start)

v1.169.5

Compare Source

Patch Changes
TanStack/router (@​tanstack/router-cli)

v1.168.0

Compare Source

Minor Changes
  • #​8855 446ce1b - Require Node ^20.19.0 || >=22.12.0 (was >=20.19), so the CommonJS builds can load ESM-only dependencies through require(esm). Node 21 and Node 22.0–22.11 do not enable it by default, so they are no longer supported.
Patch Changes
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.3.0

Compare Source

Make reactCompilerPreset work with @rolldown/plugin-babel's parallel option (#​1549)

reactCompilerPreset now refers to its Babel preset by module path instead of by function, so it can be sent to worker threads.

v6.2.1

Compare Source

Fix refreshInclude and refreshExclude options not working (#​1543)

Fix mistake from #​1516

v6.2.0

Compare Source

Add refreshInclude and refreshExclude options (#​1516)

Add refreshInclude and refreshExclude options to skip fast refresh for certain files that won't run in the browser.

Expand oxc-transform-react peer dependency range (#​1540)

The peer dependency version range for oxc-transform-react was expanded from ^0.152.0 to >=0.152.0 <0.157.0.

Expand @rolldown/plugin-babel peer dependency range (#​1541)

The peer dependency version range for @rolldown/plugin-babel was expanded from ^0.1.7 || ^0.2.0 to ^0.1.7 || ^0.2.0 || ^0.3.0.

eslint/eslint (eslint)

v10.14.0

Compare Source

Features

  • d23a7f9 feat: fix property descriptor handling in func-name-matching (#​21400) (xbinaryx)

Bug Fixes

Documentation

  • 0f94f47 docs: remove zh-hans from docs language switcher (#​21437) (lumir)
  • dab466e docs: Update README (GitHub Actions Bot)
  • 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#​21452) (Pixel)
  • 7697550 docs: Update README (GitHub Actions Bot)
  • 0c699d5 docs: Remove Tidelift commercial support (#​21416) (Milos Djermanovic)
  • 0880666 docs: update loadESLint() documentation for v10 (#​21374) (Minseon Kim)
  • e06fe87 docs: Revise AI acknowledgment options in PR template (#​21414) (Nicholas C. Zakas)

Chores

  • 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#​21462) (Francesco Trotta)
  • 6e3f988 chore: update github/codeql-action action to v4.39.1 (#​21450) (renovate[bot])
  • a031c40 chore: update ecosystem plugins (#​21445) (ESLint Bot)
  • 67d2ca2 chore: add troubleshooting page URL to circular fixes warning message (#​21429) (Milos Djermanovic)
  • 276021d chore: update github/codeql-action action to v4.39.0 (#​21432) (renovate[bot])
  • 449724e chore: update ecosystem plugins (#​21420) (ESLint Bot)
  • 8ffeb8c chore: update dependency prettier to v3.9.10 (#​21417) (renovate[bot])
schoero/eslint-plugin-better-tailwindcss (eslint-plugin-better-tailwindcss)

v4.11.0

Compare Source

compare changes

Features
  • Allow selectors to extend the default selectors (#​412)
Fixes
  • Update descriptions for unknown class ordering and positioning (204071b)
  • enforce-consistent-class-order: Update descriptions for unknown class ordering and positioning (#​432)
  • Update documentation and improve warning messages for rules (d5701ba)
  • Build config (#​433)
  • Improve strict sorting order handling for duplicate and numeric classes (#​431)
Tests
❤️ Contributors
javierbrea/eslint-plugin-boundaries (eslint-plugin-boundaries)

v7.4.1

Compare Source

Changed
  • refactor(#​549): The normalization and validation of the settings and rule options move to the new @boundaries/config package, which the plugin depends on. The plugin reports the same warnings and errors as before.
  • refactor(#​550): The descriptions of files and dependencies, the evaluation of the policies and the messages move to the new @boundaries/policies package, which the plugin depends on. The plugin reports the same errors as before.
  • chore(#​549): Type-check the plugin against the types of ESLint 9.39, which the repository develops and tests it with.
  • chore: Lint the plugin with the SonarCloud rules that eslint-plugin-sonarjs implements.
  • chore: The homepage of the package is the JS Boundaries website, the README is a short introduction that links to it, and the folder of the package in the repository is declared in the directory field that npm reads.
  • chore: The TypeScript configuration no longer uses two options that TypeScript 6 deprecates: it resolves modules with node16 instead of node10, and it no longer sets baseUrl. The build output does not change.
  • chore: Upgrade @boundaries/elements to 3.3.1.
Fixed
  • fix: Warn when the boundaries/elements, boundaries/types or boundaries/files setting is not an array. The plugin ignored it without saying why.
  • fix(#​550): When the custom message of a dependency that the dependencies, entry-point or external rule does not allow fails to render, for example because of invalid Handlebars syntax or an unknown helper, the error names the message and the policy that sets it, or the rule options. The plugin no longer prints the debug output and the matcher warnings of that dependency before failing.
  • fix(#​589): Check the dependencies written with a template literal without substitutions, inside the TypeScript assertions as, satisfies, <T> or !, with import x = require() or with a type import such as typeof import(), which were skipped: read the upgrade notes to check whether your project is affected.

v7.4.0

Compare Source

Changed
  • chore(#​570): Fix the @param tags in the TSDoc of internal functions, which named parameters that do not exist or missed some.
  • chore: Upgrade @boundaries/elements to 3.3.0.
Fixed
  • fix(#​510): Imports of Node.js built-in modules only available with the node: prefix, such as node:test or node:sqlite, have the core origin instead of external: read the upgrade notes to check whether your policies are affected.
  • fix(#​510): Some extglob patterns now match all the paths they describe, like the same patterns without extglobs (src/@(foo/**) now matches src/foo, like src/foo/**): read the upgrade notes to check whether your patterns are affected.
  • fix(#​568): With boundaries/cache enabled, which is the default, the files placed next to a linted or imported dot file, such as .lintstagedrc.js, no longer get its description or give it theirs, which could change the errors from one run to another: read the upgrade notes to find the affected files.
kucherenko/jscpd (jscpd)

v5.4.3

Compare Source

New Features
  • runJscpd() runs the jscpd binary from Node.js. require("jscpd") and import { runJscpd } from "jscpd" now export runJscpd(args, options). It finds the platform binary the way the jscpd command does and returns the result of spawnSync, so a script no longer starts a second Node.js process to run the command, and tools such as knip see that the script uses jscpd. Where the command prints an error and exits, the function throws an Error with the same message. The types are in index.d.ts. Detection still runs only in the Rust binary, and nothing parses or returns clones in JavaScript. By @​abrahamguo. (#​1238)

  • The HTML report shows both fragments of a clone and highlights the code. "Show code" used to open only the first fragment. Now it opens both side by side, or one above the other on a narrow screen, each under its file with line numbers in a gutter, and a long line scrolls inside its pane. The report highlights the code with Prism 1.30.0 again, as the v4 report did, and inlines only the languages it shows. A block inside another file, such as guide.md:typescript, keeps the lines that detection gives it. (#​1263, #​1265)

Bug Fixes
  • The GitHub Action installed the newest jscpd, whatever ref you pinned. The version input defaulted to latest, so kucherenko/jscpd@v5.4.1 installed 5.4.2 once it came out. Now an empty version installs the release that the action's own ref belongs to, so pinning the action pins jscpd, and a Dependabot bump of the action updates both. version: latest still installs the newest release. This works from v5.4.3 on: older tags still install the newest jscpd. Reported by @​dannystaple, fixed by @​sarankumar1325. (#​1240, #​1249)

  • A /* or // inside a JS or TS string ended a jscpd:ignore region. The tokenizer looked for the markers with a byte scan that took every /* and // for a comment, so 'a /* b' inside a marked region opened a comment that ran to the end marker, and the code after the string came back as clones. The markers are now found by their text, as in the other languages, so a region runs from jscpd:ignore-start to the next jscpd:ignore-end. Markers inside template literals, such as the CSS of a styled component, keep working. Reported by @​bauchdj, fixed by @​sarankumar1325. (#​1257, #​1258)

  • "Ignore this clone" in the language server broke JSX. It wrote // jscpd:ignore-start among JSX children, where the page shows it as text, and could put a ma

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


Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • Between 12:00 AM and 06:59 AM, only on Monday (* 0-6 * * 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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-minor-and-patch branch 3 times, most recently from 8968395 to 9556300 Compare November 16, 2026 12:06
@PerfectPan

Copy link
Copy Markdown
Owner

The build's static navigation check fails: after switching to zh, the client requests /agent-kit/assets/zh-BpxBZxkn.js, which the check forbids (requests used /zh URLs).

Diagnosis: the zh hero and docs text are still prerendered into index.html, but the fumadocs-mdx source bundle (source-*.js) now maps ./zh/index.mdx to a lazy import(./zh-BpxBZxkn.js) and the client actually follows it after the locale switch, so the zh document chunk ships as a runtime asset. Likely culprits in this PR: fumadocs-mdx 15.4.10 → 15.5.3 (source/chunk generation), @vitejs/plugin-react 6.1.2 → 6.3.0, or @tanstack/react-start 1.169.4 → 1.169.5 changing how the mdx page tree is chunked.

Next step needs a decision on the intended shape: either isolate the upgrade that changes the chunking, or decide the new lazy-zh behavior is acceptable and adjust static-nav-check.mjs. Splitting this PR per-package would pinpoint it fastest.

@renovate
renovate Bot force-pushed the renovate/npm-minor-and-patch branch 3 times, most recently from 1b910e1 to 028c4ce Compare November 18, 2026 07:36
@renovate
renovate Bot force-pushed the renovate/npm-minor-and-patch branch from d61747b to 42d86f3 Compare November 18, 2026 13:59

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant