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 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.3 4.3.4 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.64.1 age confidence
tailwindcss (source) devDependencies minor 4.2.2 → 4.3.3 4.3.4 age confidence
tsdown (source) devDependencies minor 0.22.14 → 0.23.4 0.23.5 age confidence
vite (source) devDependencies minor 8.2.4 → 8.3.5 8.3.6 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.14.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.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)
  • Ensure query params in imports are considered unique resources when using @tailwindcss/webpack (#​19723)
  • Canonicalization: collapse arbitrary values into shorthand utilities (e.g. px-[1.2rem] py-[1.2rem] → p-[1.2rem]) (#​19837)
  • Canonicalization: collapse border-{t,b}-* into border-y-*, border-{l,r}-* into border-x-*, and border-{t,r,b,l}-* into border-* (#​19842)
  • Canonicalization: collapse scroll-m{t,b}-* into scroll-my-*, scroll-m{l,r}-* into scroll-mx-*, and scroll-m{t,r,b,l}-* into scroll-m-* (#​19842)
  • Canonicalization: collapse scroll-p{t,b}-* into scroll-py-*, scroll-p{l,r}-* into scroll-px-*, and scroll-p{t,r,b,l}-* into scroll-p-* (#​19842)
  • Canonicalization: collapse overflow-{x,y}-* into overflow-* (#​19842)
  • Canonicalization: collapse overscroll-{x,y}-* into overscroll-* (#​19842)
  • Read from --placeholder-color instead of --background-color for placeholder-* utilities (#​19843)
  • Upgrade: ensure files are not emptied out when killing the upgrade process while it's running (#​19846)
  • Upgrade: use config.content when migrating from Tailwind CSS v3 to Tailwind CSS v4 (#​19846)
  • Upgrade: never migrate files that are ignored by git (#​19846)
  • Add .env and .env.* to default ignored content files (#​19846)
  • Canonicalization: migrate overflow-ellipsis into text-ellipsis (#​19849)
  • Canonicalization: migrate start-full → inset-s-full, start-auto → inset-s-auto, start-px → inset-s-px, and start-<number> → inset-s-<number> as well as negative versions (#​19849)
  • Canonicalization: migrate end-full → inset-e-full, end-auto → inset-e-auto, end-px → inset-e-px, and end-<number> → inset-e-<number> as well as negative versions (#​19849)
  • Canonicalization: move the - sign inside the arbitrary value -left-[9rem] → left-[-9rem] (#​19858)
  • Canonicalization: move the - sign outside the arbitrary value ml-[calc(-1*var(--width))] → -ml-(--width) (#​19858)
  • Improve performance when scanning JSONL / NDJSON files (#​19862)
  • Support NODE_PATH environment variable in standalone CLI (#​19617)
vitest-dev/vitest (@​vitest/browser)

v4.1.12

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.11

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
rolldown/tsdown (tsdown)

v0.23.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.23.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.23.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.23.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.23.0

Compare Source

   🧭 Migration Guide

Most users can upgrade directly. Before upgrading, run one final build with tsdown@0.22.14 and resolve all deprecation warnings.

  • config:
    • bundle: false → unbundle: true; bundle: true can be removed
    • outExtension → outExtensions
    • publicDir / --public-dir → copy / --copy
    • removeNodeProtocol: true → nodeProtocol: 'strip'
    • injectStyle → css.inject
  • deps:
    • inlineOnly / deps.onlyAllowBundle → deps.onlyBundle
    • skipNodeModulesBundle: true → deps.neverBundle: true
    • resolveDepSubpath now defaults to false; set it to true to preserve the previous behavior
  • dts:
    • rolldown-plugin-dts was upgraded from 0.27.13 to 0.28.5
    • dts.oxc: true → dts.generator: 'oxc'
    • dts.tsgo: true → dts.generator: 'tsgo'; oxc and tsgo objects now only configure their respective generators
    • dts.volarPlugins → dts.customLanguages; rename each language's create hook to createVolarPlugins
    • Custom languages, including vue, now throw when combined with an incompatible generator
    • dts.cjsReexport was removed; dual-format builds now generate CJS declarations in a separate pass
  • attw:
    • The default profile changed from strict to esm-only; set profile: 'strict' to preserve the previous checks
  • programmatic API:
    • build() now returns { bundles, watch }; replace const bundles = await build() with const { bundles } = await build()
  • requirements:
    • Node.js 25 is no longer supported; use ^22.18.0, ^24.11.0, or >=26.0.0
    • rolldown-plugin-dts now requires Rolldown 1.2.x
    • Legacy types and typesVersions fallbacks were removed; use TypeScript's bundler, node16, or nodenext module resolution
   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
vitejs/vite (vite)

v8.3.5

Compare Source

Bug Fixes

[!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.3
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.3
npm error   packages/js-toolkit
npm error     @studiometa/js-toolkit@4.0.0-alpha.3
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.3
npm error   packages/js-toolkit
npm error     @studiometa/js-toolkit@4.0.0-alpha.3
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.3
npm error     packages/js-toolkit
npm error       @studiometa/js-toolkit@4.0.0-alpha.3
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-05T11_12_28_853Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-05T11_12_28_853Z-debug-0.log

@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

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 review runs

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.

Previous run archived 2026-11-05T05:56:57Z

Code Review

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

This change pins several existing dependencies and upgrades others in packages/js-toolkit/package.json. The corresponding package-lock.json workspace entry was not updated, leaving the repository with stale dependency specifications.

1 issue found:

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

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest
  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes

Review usage: 46,373 in (37,433 cached) / 862 out tokens — $0.0040 (openrouter/openai/gpt-5.6-luna, thinking: low)

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

Previous run archived 2026-11-02T03:30:16Z

Code Review

Risk: Low — The dependency changes introduce no demonstrable blocking defect in the reviewed diff and are safe to merge aside from validating the updated toolchain in CI.

Pins previously ranged dependencies and updates several development-only packages, including SWC, Vite, Tailwind, VitePress, Playwright, and Vitest. No application runtime dependencies or source code were changed.

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest
  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes

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

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

Previous run archived 2026-11-02T03:26:36Z

Code Review

Risk: Low — The dependency version changes are isolated to development tooling and do not introduce an evident production-impacting defect.

Pins several previously ranged dependencies and updates a number of development packages to newer fixed versions. No concrete correctness issue is demonstrable from the provided diff.

Still open from earlier reviews (2 findings):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest
  • packages/js-toolkit/package.json:842 — issue: Update the lockfile with these dependency changes

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

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

Previous run archived 2026-11-01T07:36:24Z

Code Review

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

This MR pins the js-toolkit development dependencies and upgrades several tooling packages. The corresponding root package-lock.json was not updated and still records the previous dependency specifications and versions.

1 issue found:

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

Still open from earlier reviews (1 finding):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest

Review usage: 33,658 in (21,657 cached) / 828 out tokens — $0.0044 (openrouter/openai/gpt-5.6-luna, thinking: low)

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

Previous run archived 2026-10-29T04:14:41Z

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 versions. One Vitest integration pair is updated without updating the corresponding core package.

Still open from earlier reviews (1 finding):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest

Review usage: 28,212 in (21,083 cached) / 963 out tokens — $0.0034 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.11.0 for commit b0895f2.

Previous run archived 2026-10-24T03:46:19Z

Code Review

Risk: Low — The dependency changes do not show a demonstrable runtime or correctness defect, so this is safe to merge.

Updates and pins several development dependencies in packages/js-toolkit/package.json, including tooling for SWC, Tailwind, Vitest, Playwright, Vite, and VitePress. No production dependency or application source code is changed.

Still open from earlier reviews (1 finding):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest

Review usage: 5,512 in / 314 out tokens — $0.0018 (openrouter/openai/gpt-5.6-luna, thinking: low)

Reviewed by @weareikko/code-review v0.10.3 for commit d1e5bc6.

Previous run archived 2026-10-17T00:01:04Z

Code Review

Risk: Low — The dependency changes are isolated to development tooling and do not introduce a blocking defect.

Updates and pins the JavaScript toolkit's development dependencies, including SWC, Vite, VitePress, Tailwind CSS, Vitest browser packages, Playwright, and related tooling. No production dependencies or application source files are changed.

Still open from earlier reviews (1 finding):

  • packages/js-toolkit/package.json:843 — issue: Lockfile remains inconsistent with workspace manifest

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

Reviewed by @weareikko/code-review v0.10.3 for commit 03a1ef2.

Previous run archived 2026-10-15T19:16:48Z

Code Review

Risk: Low — The dependency version changes are limited to development tooling and do not introduce a demonstrable runtime or contract defect.

Pins previously ranged dependencies and updates several development dependencies to newer fixed versions in packages/js-toolkit/package.json. No inline issues were found.

Still open from earlier reviews (1 finding):

  • packages/js-toolkit/package.json:840 — issue: Lockfile remains inconsistent with workspace manifest

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

Reviewed by @weareikko/code-review v0.10.3 for commit 04cf865.

Previous run archived 2026-10-15T02:53:03Z

Code Review

Risk: Low — This dependency-only change has no identified blocking issues and is safe to merge aside from normal upgrade validation.

Pins previously ranged dependencies and updates several development tools to newer exact versions, including SWC, Tailwind, Vite, VitePress, Playwright, and related testing packages.

Still open from earlier reviews (1 finding):

  • packages/js-toolkit/package.json:840 — issue: Lockfile remains inconsistent with workspace manifest

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

Reviewed by @weareikko/code-review v0.10.3 for commit d570c54.

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 from c9164c6 to 91347f7 Compare November 5, 2026 05:56
@renovate
renovate Bot force-pushed the renovate/js-toolkit-dev-dependencies branch from 91347f7 to b845ba0 Compare November 5, 2026 11:12

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.

0 participants