Skip to content

chore: lib updates#18

Merged
hmbanan666 merged 1 commit intomainfrom
lib
Jan 21, 2026
Merged

chore: lib updates#18
hmbanan666 merged 1 commit intomainfrom
lib

Conversation

@hmbanan666
Copy link
Contributor

@hmbanan666 hmbanan666 commented Jan 21, 2026

Summary by cubic

Switches the queue package to use the pnpm catalog for rabbitmq-client and updates workspace settings and dev/test dependencies. This improves version consistency and maintainability across the monorepo.

  • Dependencies
    • rabbitmq-client moved to catalog:integrations (bumped to ^5.0.8).
    • Updated dev/test catalogs (eslint, commitlint, lint-staged, vitest, playwright, @types/node).
    • Added pnpm settings: publicHoistPattern, shamefullyHoist, shellEmulator, trustPolicy: no-downgrade.
    • Regenerated pnpm-lock.yaml.

Written for commit 0bca579. Summary will update on new commits.

Summary by CodeRabbit

  • Chores
    • Updated development dependencies including ESLint, Commitlint, Vitest, and Playwright to latest versions.
    • Reorganized workspace configuration and dependency catalog structure for improved maintainability.

✏️ Tip: You can customize this high-level summary in your review settings.

@hmbanan666 hmbanan666 self-assigned this Jan 21, 2026
@coderabbitai
Copy link

coderabbitai bot commented Jan 21, 2026

📝 Walkthrough

Walkthrough

The pull request updates package manager configuration and dependency versions. The packages/queue/package.json now references a cataloged dependency for rabbitmq-client. The pnpm-workspace.yaml is reorganized with new top-level workspace hoisting options and multiple dependency version updates across dev and integration catalogs.

Changes

Cohort / File(s) Summary
Queue Package Dependency
packages/queue/package.json
Updated rabbitmq-client reference from hardcoded version 5.0.7 to catalog-based reference catalog:integrations
Workspace Configuration & Catalogs
pnpm-workspace.yaml
Added top-level hoisting configuration (publicHoistPattern, shamefullyHoist, shellEmulator, trustPolicy); updated dev tool versions (@antfu/eslint-config, @commitlint/, bumpp, eslint, lint-staged, @types/node); added integrations.rabbitmq-client ^5.0.8; bumped test-related dependencies (vitest, @vitest/, playwright)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hops of joy through configs bright,
Dependencies unified, catalog in sight!
Workspace hoist with grace so keen,
Version bumps keep systems clean. 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: lib updates' is vague and generic; it uses non-descriptive terms like 'lib updates' that don't convey meaningful information about the specific changes made. Consider a more specific title that highlights the main change, such as 'chore: update workspace dependencies and add rabbitmq-client integration catalog' or similar.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

1 issue found across 3 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="pnpm-workspace.yaml">

<violation number="1" location="pnpm-workspace.yaml:32">
P2: `@types/node` v25 targets Node 25 APIs, but this repo’s runtime is Node 24. Keep `@types/node` on the same major version as the runtime to avoid type declarations for APIs that don’t exist at runtime.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

vitest: ^4.0.17
types:
'@types/node': ^24.10.1
'@types/node': ^25.0.9
Copy link

@cubic-dev-ai cubic-dev-ai bot Jan 21, 2026

Choose a reason for hiding this comment

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

P2: @types/node v25 targets Node 25 APIs, but this repo’s runtime is Node 24. Keep @types/node on the same major version as the runtime to avoid type declarations for APIs that don’t exist at runtime.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At pnpm-workspace.yaml, line 32:

<comment>`@types/node` v25 targets Node 25 APIs, but this repo’s runtime is Node 24. Keep `@types/node` on the same major version as the runtime to avoid type declarations for APIs that don’t exist at runtime.</comment>

<file context>
@@ -1,34 +1,39 @@
+    vitest: ^4.0.17
   types:
-    '@types/node': ^24.10.1
+    '@types/node': ^25.0.9
 
 ignoredBuiltDependencies:
</file context>
Suggested change
'@types/node': ^25.0.9
'@types/node': ^24.10.1
Fix with Cubic

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@pnpm-workspace.yaml`:
- Around line 14-25: Upgrade note: the '@antfu/eslint-config' v7 bump requires
migrating the perfectionist plugin options to v5 (kebab-case → camelCase and
some default changes); open your ESLint configuration where the "perfectionist"
rule is defined (e.g., rules["perfectionist"] or .eslintrc.*), update all option
keys from kebab-case to camelCase, adjust any overridden defaults to match v5
semantics, and then run npx eslint . --fix to validate and auto-fix formatting
issues introduced by the rule change.
- Around line 31-32: The package version for `@types/node` is incompatible with
the project's Node.js engine; change the `@types/node` entry from ^25.0.9 to a
^24.x range to match the project's Node.js >=24.11.1 requirement, or
alternatively update the project's engine requirement to >=25.0.0 if you intend
to move to Node.js 25; update the `@types/node` version string (symbol:
'@types/node') or the engine field accordingly so the types and runtime Node
version align.

Comment on lines 14 to +25
dev:
'@antfu/eslint-config': ^6.2.0
'@commitlint/cli': ^20.1.0
'@commitlint/config-conventional': ^20.0.0
bumpp: ^10.3.1
eslint: ^9.39.1
'@antfu/eslint-config': ^7.2.0
'@commitlint/cli': ^20.3.1
'@commitlint/config-conventional': ^20.3.1
bumpp: ^10.4.0
eslint: ^9.39.2
husky: ^9.1.7
lint-staged: ^16.2.6
lint-staged: ^16.2.7
typescript: ^5.9.3
unbuild: ^3.6.1
integrations:
rabbitmq-client: ^5.0.8
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion | 🟠 Major

🧩 Analysis chain

🌐 Web query:

@antfu/eslint-config v7 breaking changes migration guide

💡 Result:

Summary — what changed in @antfu/eslint-config v7

  • The v7 release’s documented breaking change is: upgrade of the perfectionist plugin to v5.0.x. [1]

What you need to do (migration steps)

  1. Upgrade the preset:
    • npm: npm install -D @antfu/eslint-config@^7
    • yarn/pnpm: accordingly. [1]
  2. Install/upgrade perfectionist (if you pin it yourself) — align to perfectionist v5:
    • npm install -D eslint-plugin-perfectionist@^5
    • (If you rely on the preset’s deps, just run install; the preset will pull the new version.) [1]
  3. Check perfectionist configuration options in your config:
    • Perfectionist v5 introduced breaking option changes (examples: renames from kebab-case to camelCase, some option defaults changed such as case-ignoring becoming enabled, and other option renames/semantic changes). Review any perfectionist rule options you override and adapt names/values as needed. [2][3]
  4. Run lint and autofix (and CI) and address any changed rule behavior:
    • npx eslint . --fix
    • Fix any new/changed failures introduced by the plugin upgrade.

Links / sources

  • antfu/eslint-config v7 release notes (breaking change: upgrade perfectionist → v5). [1]
  • Perfectionist (changelog / v5 breaking changes and notes about option renames and defaults). [2][3]

If you want, I can:

  • Inspect your eslint config (paste it) and produce the exact edits needed for perfectionist v5 option renames and defaults.

Check for perfectionist v5 option compatibility after @antfu/eslint-config upgrade.

The v7 upgrade includes a mandatory breaking change: perfectionist plugin upgrades to v5.0.x. Perfectionist v5 renames options from kebab-case to camelCase and changes some defaults. After upgrading, review and update any custom perfectionist rule options in your ESLint config, then run npx eslint . --fix to validate against the new rule behavior.

The new integrations catalog is a clean way to separate integration-specific dependencies.

🤖 Prompt for AI Agents
In `@pnpm-workspace.yaml` around lines 14 - 25, Upgrade note: the
'@antfu/eslint-config' v7 bump requires migrating the perfectionist plugin
options to v5 (kebab-case → camelCase and some default changes); open your
ESLint configuration where the "perfectionist" rule is defined (e.g.,
rules["perfectionist"] or .eslintrc.*), update all option keys from kebab-case
to camelCase, adjust any overridden defaults to match v5 semantics, and then run
npx eslint . --fix to validate and auto-fix formatting issues introduced by the
rule change.

Comment on lines 31 to +32
types:
'@types/node': ^24.10.1
'@types/node': ^25.0.9
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check `@types/node` version information from npm registry
curl -s https://registry.npmjs.org/@types/node | jq '.["dist-tags"] as $tags | {
  "latest": $tags.latest,
  "next": $tags.next
}, (.versions | keys | map(select(startswith("25."))) | sort)'

Repository: nextorders/queue

Length of output: 223


🏁 Script executed:

#!/bin/bash
# Check Node.js version requirement and TypeScript version in the project
echo "=== Checking package.json for Node.js and TypeScript versions ==="
find . -maxdepth 2 -name "package.json" -type f | head -5 | xargs grep -l "engines\|typescript" | head -1 | xargs cat | jq '.engines, .devDependencies.typescript'

echo "=== Checking if pnpm-workspace.yaml has any engine specs ==="
cat pnpm-workspace.yaml | grep -A 5 "packages\|engines" || true

Repository: nextorders/queue

Length of output: 367


🏁 Script executed:

#!/bin/bash
# Check TypeScript version and any other Node.js version hints
echo "=== Full pnpm-workspace.yaml ==="
cat pnpm-workspace.yaml

echo ""
echo "=== Checking root package.json engine specs ==="
cat package.json | jq '.engines' 2>/dev/null || echo "No engines field found"

Repository: nextorders/queue

Length of output: 920


Update @types/node to v24.x or upgrade Node.js requirement to v25+.

@types/node v25.x aligns with Node.js v25, but this project requires Node.js >=24.11.1. Using v25 types with Node.js v24 creates a mismatch and may result in missing or incorrect type definitions. Either downgrade @types/node to ^24.x to match the Node.js v24 requirement, or update the engine requirement to >=25.0.0 if upgrading to Node.js v25.

🤖 Prompt for AI Agents
In `@pnpm-workspace.yaml` around lines 31 - 32, The package version for
`@types/node` is incompatible with the project's Node.js engine; change the
`@types/node` entry from ^25.0.9 to a ^24.x range to match the project's Node.js
>=24.11.1 requirement, or alternatively update the project's engine requirement
to >=25.0.0 if you intend to move to Node.js 25; update the `@types/node` version
string (symbol: '@types/node') or the engine field accordingly so the types and
runtime Node version align.

@hmbanan666 hmbanan666 merged commit 95fd799 into main Jan 21, 2026
5 checks passed
@hmbanan666 hmbanan666 deleted the lib branch January 21, 2026 08:47
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