Skip to content

Conversation

xingyu4j
Copy link

@xingyu4j xingyu4j commented Oct 14, 2025

Description

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
  • Run the tests with pnpm test.
  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • Chores
    • Upgraded workspace tooling and related dependencies to newer versions for improved stability and compatibility.
    • Updated the declared package manager version to align with the latest supported tooling.
  • Style
    • Minor formatting cleanup in a chart rendering utility; no changes to behavior or output.

Copy link

changeset-bot bot commented Oct 14, 2025

⚠️ No Changeset found

Latest commit: f9720bd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Oct 14, 2025

Walkthrough

Updates the root packageManager to [email protected], bumps multiple dependency versions in pnpm-workspace.yaml, and applies a minor formatting change (trailing comma) in a TypeScript utility file. No logic, control flow, or exported API changes.

Changes

Cohort / File(s) Summary
Package manager declaration
package.json
Update packageManager from [email protected] to [email protected].
Workspace dependency catalog updates
pnpm-workspace.yaml
Bump versions for multiple catalog entries (tooling, linting, UI/Vue ecosystem, Playwright, etc.); no additions/removals, only version updates.
Formatting tweak (no runtime change)
packages/effects/plugins/src/echarts/use-echarts.ts
Add trailing comma in renderEcharts function parameter list; no behavior change.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

chore

Suggested reviewers

  • anncwb
  • vince292007
  • mynetfan

Poem

A rabbit taps the version drum—thump, thump, thump!
pnpm hops ahead with a tidy little jump.
The garden’s deps are pruned and neat,
commas trail like rhythmic beat.
I twitch my whiskers, merge with glee—
configs aligned, carrot tea! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description is merely the unfilled template with no summary of the actual dependency updates, missing any context or rationale, and the “Type of change” checkboxes are left unselected along with an empty checklist. Therefore it does not meet the repository’s requirement to describe changes, specify change types, or confirm completion of tests and documentation. Please add a detailed description of which dependencies were updated and why, select the appropriate “Type of change” checkbox, and complete the checklist to confirm tests, documentation, and changelog updates as required by the template.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (1 passed)
Check name Status Explanation
Title Check ✅ Passed The title “chore: update deps” clearly and concisely indicates that this pull request updates project dependencies without implying functional changes. It aligns with conventional commit standards and accurately reflects the main scope of version bumps in package.json, pnpm-workspace.yaml, and minor formatting updates. Therefore it adequately summarizes the change at a glance.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
Contributor

@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: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
packages/effects/plugins/src/echarts/use-echarts.ts (1)

60-68: Bug: theme argument is ignored when set to 'light' due to operator precedence

t || isDark.value ? 'dark' : null evaluates as (t || isDark.value) ? 'dark' : null, forcing 'dark' even when t === 'light'. Use nullish coalescing or parentheses.

Apply this fix:

-    chartInstance = echarts.init(el, t || isDark.value ? 'dark' : null);
+    // Use provided theme if defined; otherwise use dark when preference is dark
+    chartInstance = echarts.init(el, t ?? (isDark.value ? 'dark' : null));
pnpm-workspace.yaml (1)

16-194: Fix check-circular script failure

  • vsh check-circular errors with ERR_MODULE_NOT_FOUND: cannot find jiti/lib/jiti.mjs (see internal/node-utils/scripts/vsh). Ensure the jiti dependency is installed at the expected version or update the import paths in scripts/vsh and internal/node-utils.
  • Rerun full CI (pnpm run check, turbo run typecheck, build, test:unit, test:e2e) and confirm all steps pass.
🧹 Nitpick comments (2)
packages/effects/plugins/src/echarts/use-echarts.ts (1)

70-105: Unbounded retries when element stays hidden

Recursive defers via useTimeoutFn(... renderEcharts(...), 30) have no cap, causing potential infinite retry/timer churn if the element never becomes visible.

Consider a max-attempt counter or an AbortSignal. Example:

-  const renderEcharts = (
-    options: EChartsOption,
-    clear = true,
-  ): Promise<Nullable<echarts.ECharts>> => {
+  const renderEcharts = (
+    options: EChartsOption,
+    clear = true,
+    _attempt = 0,
+  ): Promise<Nullable<echarts.ECharts>> => {
     cacheOptions = options;
     const currentOptions = {
       ...options,
       ...getOptions.value,
     };
     return new Promise((resolve) => {
-      if (chartRef.value?.offsetHeight === 0) {
+      if (chartRef.value?.offsetHeight === 0) {
+        if (_attempt > 50) return resolve(null);
         useTimeoutFn(async () => {
-          resolve(await renderEcharts(currentOptions));
+          resolve(await renderEcharts(currentOptions, clear, _attempt + 1));
         }, 30);
         return;
       }
       nextTick(() => {
         const el = getChartEl();
         if (isElHidden(el)) {
+          if (_attempt > 50) return resolve(null);
           useTimeoutFn(async () => {
-            resolve(await renderEcharts(currentOptions));
+            resolve(await renderEcharts(currentOptions, clear, _attempt + 1));
           }, 30);
           return;
         }
package.json (1)

101-102: Align engines.pnpm with packageManager to avoid toolchain skew

You updated packageManager to [email protected], but engines.pnpm is >=9.12.0. Recommend aligning to the same major (and ideally exact/min required) to reduce CI/dev mismatches.

Proposed tweak:

   "engines": {
     "node": ">=20.10.0",
-    "pnpm": ">=9.12.0"
+    "pnpm": ">=10.18.2"
   },
   "packageManager": "[email protected]",

Please confirm:

  • Corepack is enabled and pnpm 10.18.2 is prepared in CI.
  • A fresh install works: pnpm -v shows 10.18.2 and pnpm -w install succeeds.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 03ce030 and f9720bd.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (3)
  • package.json (1 hunks)
  • packages/effects/plugins/src/echarts/use-echarts.ts (1 hunks)
  • pnpm-workspace.yaml (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: post-update (ubuntu-latest)
  • GitHub Check: post-update (windows-latest)
🔇 Additional comments (1)
packages/effects/plugins/src/echarts/use-echarts.ts (1)

70-74: Nit: trailing comma change is fine

No behavior change; signature remains compatible.

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