Skip to content

chore(deps): pin dependencies - #881

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/js-toolkit-dev-dependencies
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/js-toolkit-dev-dependencies

Conversation

@renovate

@renovate renovate Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Pending Age Confidence
@rollup/plugin-swc (source) devDependencies pin ^0.4.1 → 0.4.1 age confidence
@shikijs/vitepress-twoslash (source) devDependencies minor 4.0.2 → 4.6.0 age confidence
@studiometa/tailwind-config devDependencies patch 3.0.0 → 3.0.1 3.0.2 age confidence
@swc/core (source) devDependencies pin ^1.15.47 → 1.16.22 age confidence
@tailwindcss/vite (source) devDependencies minor 4.2.2 → 4.3.5 age confidence
@vitest/browser (source) devDependencies patch 4.1.10 → 4.1.12 age confidence
@vitest/browser-playwright (source) devDependencies patch 4.1.10 → 4.1.12 age confidence
focus-trap devDependencies pin ^7.8.0 → 7.8.0 age confidence
playwright (source) devDependencies pin ^1.50.0 → 1.65.1 age confidence
tailwindcss (source) devDependencies minor 4.2.2 → 4.3.5 age confidence
tsdown (source) devDependencies minor 0.22.14 → 0.23.7 age confidence
vite (source) devDependencies minor 8.2.4 → 8.3.8 age confidence
vitepress (source) devDependencies patch 2.0.0-alpha.19 → 2.0.0-alpha.21 age confidence
vitepress-plugin-llms devDependencies minor 1.12.0 → 1.15.0 age confidence

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

shikijs/shiki (@​shikijs/vitepress-twoslash)

v4.6.0

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.4.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.4.2

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.4.1

Compare Source

   🚀 Features
    View changes on GitHub

v4.4.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.3.1

Compare Source

   🚀 Features
    View changes on GitHub

v4.3.0

Compare Source

   🚀 Features
    View changes on GitHub

v4.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
studiometa/tailwind-config (@​studiometa/tailwind-config)

v3.0.1

Compare Source

Changed
  • Replace the ## [Unreleased] section with .changelog/ fragments checked on pull requests by weareikko/changelog, and release from the publish-and-release workflow, which bumps the version, folds the fragments into CHANGELOG.md, tags, publishes to npm and creates the GitHub release (#​137)
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)

v4.3.3

Compare Source

Fixed
  • Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#​20297)
  • Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#​20298)
  • Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#​20292)
  • Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#​20299)
  • Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#​20302)
  • Parse selectors like [data-foo]div as two selectors instead of one (#​20303)
  • Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#​20310)
  • Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#​20124)
  • Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#​20314)
  • Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#​20319)
  • Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#​20325)
  • Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#​20318)
  • Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#​20329)
  • Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#​20335)
  • Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#​20336)

v4.3.2

Compare Source

Fixed
  • Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#​20229)
  • Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#​20242)
  • Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#​20245)
  • Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#​20246)
  • Allow @variant rules used in addBase(…) to use custom variants defined later (#​20247)
  • Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#​20259)
  • Generate font-size instead of color declarations for text-[--spacing(…)] (#​20260)
  • Prevent @source patterns from scanning unrelated sibling files and folders (#​20263)
  • Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#​20269)
  • Extract class candidates from conditional Maud syntax like p.text-black[condition] (#​20269)
  • Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#​20277)
  • Support class suggestions for named opacity modifiers from --opacity theme values (#​20287)
  • Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#​20289)

v4.3.1

Compare Source

Added
  • Add --silent option to suppress output in @tailwindcss/cli (#​20100)
Fixed
  • Remove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+ (#​20028)
  • Canonicalization: don't crash when plugin utilities throw for unsupported values (#​20052)
  • Allow @apply to be used with CSS mixins (#​19427)
  • Ensure not-* correctly negates @container queries, including style(…) queries (#​20059)
  • Ensure drop-shadow-* color utilities work with custom shadow values containing calc(…) (#​20080)
  • Fix 'Sourcemap is likely to be incorrect' warnings when using @tailwindcss/vite (#​20103)
  • Ensure @tailwindcss/webpack can be installed in Rspack projects without requiring webpack as a peer dependency (#​20027)
  • Canonicalization: don't suggest invalid calc(…) expressions (e.g. px-[calc(1rem+0px)] → px-[calc(1rem+0)]) (#​20127)
  • Canonicalization: avoid suggesting large spacing-scale values for arbitrary lengths (e.g. left-[99999px] → left-[99999px], not left-24999.75) (#​20130)
  • Ensure @tailwindcss/cli in --watch mode recovers when a tracked dependency is deleted and restored (#​20137)
  • Ensure standalone @tailwindcss/cli binaries are ignored when scanning for class candidates (#​20139)
  • Ensure class candidates are extracted from Twig addClass(…) and removeClass(…) calls (#​20198)
  • Don't crash in the Ruby or Vue preprocessors when scanning files containing invalid UTF-8 bytes (#​19588)
  • Allow @variant to be used inside addBase (#​19480)
  • Ensure @source globs with symlinks are preserved (#​20203)
  • Ensure later @source rules can re-include files excluded by earlier @source not rules (#​20203)
  • Upgrade: don't migrate empty class rules to invalid @utility rules (#​20205)
  • Ensure transitions between inset-shadow-none and other inset shadows work correctly (#​20208)
  • Ensure explicitly referenced @source directories are scanned even when ignored by git (#​20214)
  • Ensure @source globs ending in **/* preserve dynamic path segments to avoid scanning too many files (#​20217)
  • Canonicalization: don't fold calc(…) divisions when the result would require high precision (e.g. w-[calc(100%/3.5)] → w-[calc(100%/3.5)], not w-[28.571428571428573%]) (#​20221)
  • Serve ESM type declarations to ESM importers of @tailwindcss/postcss (#​20228)
Changed
  • Generate 0 instead of calc(var(--spacing) * 0) for spacing utilities like m-0 and left-0 (#​20196)
  • Generate var(--spacing) instead of calc(var(--spacing) * 1) for spacing utilities like m-1 and left-1 (#​20196)

v4.3.0

Compare Source

Added
  • Add @container-size utility (#​18901)
  • Add scrollbar-{auto,thin,none} utilities for scrollbar-width, and scrollbar-thumb-* / scrollbar-track-* color utilities for scrollbar-color (#​19981, #​20019)
  • Add scrollbar-gutter-* utilities (#​20018)
  • Add zoom-* utilities (#​20020)
  • Add tab-* utilities (#​20022)
  • Allow using @variant with stacked variants (e.g. @variant hover:focus { … }) (#​19996)
  • Allow using @variant with compound variants (e.g. @variant hover, focus { … }) (#​19996)
  • Support --default(…) in --value(…) and --modifier(…) for functional @utility definitions (#​19989)
Fixed
  • Ensure @plugin resolves package JavaScript entries instead of browser CSS entries when using @tailwindcss/vite (#​19949)
  • Fix relative @import and @plugin paths resolving from the wrong directory when using @tailwindcss/vite (#​19965)
  • Ensure CSS files containing @variant are processed by @tailwindcss/vite (#​19966)
  • Resolve imports relative to base when result.opts.from is not provided when using @tailwindcss/postcss (#​19980)
  • Canonicalization: preserve significant _ whitespace in arbitrary values (#​19986)
  • Canonicalization: add parentheses when removing whitespace from arbitrary values would hurt readability (e.g. w-[calc(100%---spacing(60))] → w-[calc(100%-(--spacing(60)))]) (#​19986)
  • Canonicalization: preserve the original unit in arbitrary values instead of normalizing to base units (e.g. -mt-[20in] → mt-[-20in], not mt-[-1920px]) (#​19988)
  • Canonicalization: migrate arbitrary :has() variants from [&:has(…)] to has-[…] (#​19991)
  • Upgrade: don’t migrate inline style attributes (e.g. style="flex-grow: 1" → style="flex-grow: 1", not style="grow: 1") (#​19918)
  • Allow multiple @utility definitions with the same name but different value types (#​19777)
  • Export missing PluginWithConfig type from tailwindcss/plugin to fix errors when inferring plugin config types (#​19707)
  • Ensure start and end legacy utilities without values do not generate CSS (#​20003)
  • Ensure --value(…) is required in functional @utility definitions (#​20005)
  • Canonicalization: preserve required whitespace around operators in negated arbitrary values (e.g. -left-[(var(--a)+var(--b))]) (#​20011)

v4.2.4

Compare Source

Fixed
  • Ensure imports in @import and @plugin still resolve correctly when using Vite aliases in @tailwindcss/vite (#​19947)

v4.2.3

Compare Source

Fixed
  • Canonicalization: improve canonicalization for tracking-* utilities by preferring non-negative utilities (e.g. -tracking-tighter → tracking-wider) (#​19827)
  • Fix crash due to invalid characters in candidate (exceeding valid unicode code point range) (#​19829

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 added the renovate Renovate bot label Oct 12, 2026
@renovate

renovate Bot commented Oct 12, 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 error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @studiometa/js-toolkit@4.0.0-alpha.5
npm error Found: vitest@4.1.10
npm error node_modules/vitest
npm error   dev vitest@"4.1.10" from @studiometa/js-toolkit@4.0.0-alpha.5
npm error   packages/js-toolkit
npm error     @studiometa/js-toolkit@4.0.0-alpha.5
npm error     node_modules/@studiometa/js-toolkit
npm error       workspace packages/js-toolkit from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"4.1.12" from @vitest/browser@4.1.12
npm error node_modules/@vitest/browser
npm error   dev @vitest/browser@"4.1.12" from @studiometa/js-toolkit@4.0.0-alpha.5
npm error   packages/js-toolkit
npm error     @studiometa/js-toolkit@4.0.0-alpha.5
npm error     node_modules/@studiometa/js-toolkit
npm error       workspace packages/js-toolkit from the root project
npm error   @vitest/browser@"4.1.12" from @vitest/browser-playwright@4.1.12
npm error   node_modules/@vitest/browser-playwright
npm error     dev @vitest/browser-playwright@"4.1.12" from @studiometa/js-toolkit@4.0.0-alpha.5
npm error     packages/js-toolkit
npm error       @studiometa/js-toolkit@4.0.0-alpha.5
npm error       node_modules/@studiometa/js-toolkit
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 /runner/cache/others/npm/_logs/2026-11-16T21_41_33_980Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-16T21_41_33_980Z-debug-0.log

@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Code Review

Risk: Low — The dependency updates are scoped to packages/js-toolkit/package.json and introduce no demonstrable runtime or contract defects; safe to merge.

Pins previously ranged dependencies and updates several development dependencies, including Shiki, Tailwind, Vite, Playwright, tsdown, and VitePress. The related Tailwind and Vitest package versions remain aligned.

Still open from earlier reviews (6 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes
  • packages/js-toolkit/package.json:843 — issue: Regenerate the lockfile for updated dependency pins
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for changed dependencies
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for updated workspace dependencies

Review usage: 5,504 in / 282 out tokens — $0.0017 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit 8aefaee.

Previous review runs

Previous run archived 2026-11-14T07:54:46Z

Code Review

Risk: Low — The dependency changes are isolated to development tooling and do not introduce an evident runtime or data-integrity defect.

Pins several previously ranged dependencies and updates multiple development tools to newer versions in packages/js-toolkit/package.json. No demonstrable issues were found in the provided diff.

Still open from earlier reviews (6 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes
  • packages/js-toolkit/package.json:843 — issue: Regenerate the lockfile for updated dependency pins
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for changed dependencies
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for updated workspace dependencies

Review usage: 5,506 in / 208 out tokens — $0.0016 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit 7f4f796.

Previous run archived 2026-11-13T19:38:50Z

Code Review

Risk: Medium — issues that should be addressed before merge.

This change pins and updates the js-toolkit workspace dependencies. The corresponding root lockfile was not updated to reflect the new dependency specifications and versions.

1 issue found:

  • issue — packages/js-toolkit/package.json:842 — Regenerate the lockfile for updated workspace dependencies

Still open from earlier reviews (5 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes
  • packages/js-toolkit/package.json:843 — issue: Regenerate the lockfile for updated dependency pins
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for changed dependencies

Review usage: 41,002 in (27,879 cached) / 1,130 out tokens — $0.0052 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit 942d162.

Previous run archived 2026-11-12T11:48:13Z

Code Review

Risk: High — blocking issues remain — resolve them before merge.

This change pins several existing development dependencies and upgrades others, including the Vite, VitePress, Tailwind, SWC, and browser-testing toolchains. The corresponding package-lock.json was not updated in this MR.

1 issue found:

  • issue (blocking) — packages/js-toolkit/package.json:843 — Regenerate the lockfile for changed dependencies

Still open from earlier reviews (4 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes
  • packages/js-toolkit/package.json:843 — issue: Regenerate the lockfile for updated dependency pins

Review usage: 39,393 in (26,854 cached) / 876 out tokens — $0.0047 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit b28ebdb.

Previous run archived 2026-11-09T17:44:56Z

Code Review

Risk: Low — The dependency version changes are safe to merge; no concrete defects are evident in the reviewed diff.

Pins previously ranged dependencies and updates several development dependencies to newer fixed versions. The changes are limited to packages/js-toolkit/package.json and do not alter application or runtime code.

Still open from earlier reviews (4 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes
  • packages/js-toolkit/package.json:843 — issue: Regenerate the lockfile for updated dependency pins

Review usage: 5,508 in (3,066 cached) / 274 out tokens — $0.0010 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit ef1ce88.

Previous run archived 2026-11-09T00:41:51Z

Code Review

Risk: Low — no blocking issues; safe to merge aside from nits.

This change pins previously ranged development dependencies and updates several tooling packages to newer exact versions. The browser-specific Vitest packages are moved to 4.1.12 while vitest remains at 4.1.10.

Still open from earlier reviews (4 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes
  • packages/js-toolkit/package.json:843 — issue: Regenerate the lockfile for updated dependency pins

Review usage: 15,803 in (8,574 cached) / 814 out tokens — $0.0030 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit d2e0fa3.

Previous run archived 2026-11-09T00:39:14Z

Code Review

Risk: Medium — issues that should be addressed before merge.

This MR pins existing dependencies and updates several development-tool versions in packages/js-toolkit/package.json. The corresponding root package-lock.json was not updated and still records the previous dependency specifications and resolutions.

1 issue found:

  • issue — packages/js-toolkit/package.json:843 — Regenerate the lockfile for updated dependency pins

Still open from earlier reviews (3 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest
  • packages/js-toolkit/package.json:843 — issue (blocking): Regenerate the lockfile for the dependency changes

Review usage: 53,665 in (40,236 cached) / 935 out tokens — $0.0053 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit e1c163b.

Previous run archived 2026-11-08T14:14:29Z

Code Review

Risk: High — blocking issues remain — resolve them before merge.

This change pins and upgrades the js-toolkit development dependencies in packages/js-toolkit/package.json. The corresponding root package-lock.json entries remain at the previous versions and ranges.

1 issue found:

  • issue (blocking) — packages/js-toolkit/package.json:843 — Regenerate the lockfile for the dependency changes

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest

Review usage: 39,050 in (27,189 cached) / 992 out tokens — $0.0047 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit df6a4ab.

Previous run archived 2026-11-06T19:24:07Z

Code Review

Risk: Low — The dependency updates are version-pinned and should be safe to merge, with no demonstrable defects in the diff.

This change replaces floating version ranges and updates several development dependencies to newer fixed versions. No application or runtime source code is modified.

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest

Review usage: 5,507 in / 200 out tokens — $0.0016 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit 90110e9.

Previous run archived 2026-11-06T00:58:02Z

Code Review

Risk: Low — The dependency changes are isolated to development tooling and pin the listed packages to exact versions; no blocking issues were found.

Updates the js-toolkit development dependencies, including version upgrades for documentation, build, styling, and test tooling. The package manifest now uses exact versions for the affected dependencies.

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest

Review usage: 11,625 in (5,505 cached) / 449 out tokens — $0.0022 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit b845ba0.

Previous run archived 2026-11-05T11:13:19Z

Code Review

Risk: Low — The dependency pins and version updates are confined to development tooling, with no concrete runtime defect visible in the diff.

Updates the js-toolkit development dependencies by pinning previously ranged versions and advancing several toolchain packages. No blocking or actionable issues were found.

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes
  • packages/js-toolkit/package.json:842 — issue: Regenerate the lockfile for the updated dependency manifest

Review usage: 5,508 in / 239 out tokens — $0.0017 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.1 for commit 91347f7.

Comment thread packages/js-toolkit/package.json Outdated
"@rollup/plugin-swc": "^0.4.1",
"@shikijs/vitepress-twoslash": "4.0.2",
"@rollup/plugin-swc": "0.4.1",
"@shikijs/vitepress-twoslash": "4.5.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue: Lockfile remains inconsistent with workspace manifest

The workspace entry in package-lock.json still records the previous dependency versions and ranges, including vite: "8.2.1", while this manifest now requires different values. npm ci validates this relationship and exits instead of installing dependencies; regenerate and commit the lockfile.

Confidence: high.


Reviewed by @weareikko/code-review v0.9.9 for commit 4ec4dc7.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 4 times, most recently from 03a1ef2 to d1e5bc6 Compare October 17, 2026 00:00
@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 2 times, most recently from b0895f2 to 419cef6 Compare October 29, 2026 04:13
"@tailwindcss/vite": "4.2.2",
"@vitest/browser": "4.1.10",
"@vitest/browser-playwright": "4.1.10",
"@rollup/plugin-swc": "0.4.1",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue: Update the lockfile with these dependency changes

The committed package-lock.json still records the old js-toolkit dependency ranges and versions, including @shikijs/vitepress-twoslash at 4.0.2, while this manifest requires 4.5.0 and other updated exact versions. Because the lockfile is stale, npm ci will reject the manifest/lockfile mismatch and clean installs will not use the pinned dependencies; regenerate and commit package-lock.json.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit 419cef6.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 3 times, most recently from 0c6e37c to c9164c6 Compare November 2, 2026 03:29
"@tailwindcss/vite": "4.2.2",
"@vitest/browser": "4.1.10",
"@vitest/browser-playwright": "4.1.10",
"@rollup/plugin-swc": "0.4.1",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue: Regenerate the lockfile for the updated dependency manifest

The workspace entry in package-lock.json still declares the previous versions and ranges, including @rollup/plugin-swc as ^0.4.1 and vite as 8.2.4, while this manifest changes them. npm ci validates the lockfile against workspace manifests and will reject this mismatch; regenerate package-lock.json and commit the resulting dependency resolutions.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit c9164c6.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 4 times, most recently from 90110e9 to df6a4ab Compare November 6, 2026 19:23
"@vitest/browser": "4.1.10",
"@vitest/browser-playwright": "4.1.10",
"@rollup/plugin-swc": "0.4.1",
"@shikijs/vitepress-twoslash": "4.6.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue (blocking): Regenerate the lockfile for the dependency changes

The package manifest now requires @shikijs/vitepress-twoslash 4.6.0 and other changed versions, but package-lock.json still records the old packages/js-toolkit dependency specification, including 4.0.2. A clean npm ci detects this manifest-lockfile mismatch and fails before dependencies are installed. Regenerate and commit the root lockfile.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit df6a4ab.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch from df6a4ab to e1c163b Compare November 8, 2026 14:13
"@vitest/browser": "4.1.10",
"@vitest/browser-playwright": "4.1.10",
"@rollup/plugin-swc": "0.4.1",
"@shikijs/vitepress-twoslash": "4.6.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue: Regenerate the lockfile for updated dependency pins

The workspace manifest now declares different dependency ranges and versions, but the committed root package-lock.json still records the old values, such as vite 8.2.4 and @tailwindcss/vite 4.2.2. npm's lockfile validation will reject this mismatch during npm ci, so regenerate and commit package-lock.json with these changes.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit e1c163b.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 3 times, most recently from ef1ce88 to b28ebdb Compare November 9, 2026 17:43
"@vitest/browser": "4.1.10",
"@vitest/browser-playwright": "4.1.10",
"@rollup/plugin-swc": "0.4.1",
"@shikijs/vitepress-twoslash": "4.6.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue (blocking): Regenerate the lockfile for changed dependencies

The committed package-lock.json still records the previous packages/js-toolkit dependency specifications, including vite 8.2.4, vitepress 2.0.0-alpha.19, and @vitest/browser 4.1.10, while this manifest requires different versions. npm ci validates workspace manifests against the lockfile and will reject this inconsistent tree instead of installing it. Run the package manager install/update and commit the resulting lockfile.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit b28ebdb.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch from b28ebdb to 942d162 Compare November 12, 2026 11:47
"@tailwindcss/vite": "4.2.2",
"@vitest/browser": "4.1.10",
"@vitest/browser-playwright": "4.1.10",
"@rollup/plugin-swc": "0.4.1",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

issue: Regenerate the lockfile for updated workspace dependencies

The root package-lock.json still records the previous packages/js-toolkit dependency specifications, including @shikijs/vitepress-twoslash at 4.0.2 and vite at 8.2.4, while this manifest contains different specs and versions. npm ci validates workspace manifests against the lockfile and will reject this repository until package-lock.json is regenerated and committed.

Confidence: high.


Reviewed by @weareikko/code-review v0.11.1 for commit 942d162.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 2 times, most recently from 7f4f796 to 43f247b Compare November 13, 2026 22:29
@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch 2 times, most recently from 8aefaee to 093e8d9 Compare November 16, 2026 09:01
@titouanmathis

Copy link
Copy Markdown
Contributor

Renovate review (high risk: vite 8.2.4 → 8.3.8, tsdown 0.22 → 0.23, vitest browser packages): left open.

Checks: CI on head 093e8d93. renovate/artifacts fails and npm ci fails in every CI job: package-lock.json was not regenerated. npm returns ERESOLVE: @vitest/browser 4.1.12 needs vitest 4.1.12, but vitest stays on 4.1.10 in this PR. renovate/stability-days is also still pending.

Needed: group vitest with all @vitest/* packages so that they move together, then let Renovate regenerate the lockfile. The main branch is green.

@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch from a516e82 to 5ef9e75 Compare November 16, 2026 09:40

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

renovate Renovate bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant