chore: bump @rc-component/trigger version

[aojunhao123]

Summary by CodeRabbit

• Chore
  • 升级了项目依赖，提升了系统性能和稳定性。
• New Features
  • 优化了弹窗动画效果，实现更流畅自然的过渡，改善了整体用户体验。

[coderabbitai]

Walkthrough

此次更改更新了 package.json 中 @rc-component/trigger 依赖的版本号，从 ^2.0.0 升级至 ^3.0.0。同时在 src/KeywordTrigger.tsx 文件中调整了弹出层动画的传参方式，由原来直接传递 popupTransitionName 改为使用包含 motionName 键的 popupMotion 对象。

Changes

文件	更改摘要
package.json	更新 @rc-component/trigger 版本：^2.0.0 → ^3.0.0
src/KeywordTrigger.tsx	调整弹出层动画传参方式，由 popupTransitionName 改为 popupMotion: { motionName }

Sequence Diagram(s)

sequenceDiagram
    participant KT as KeywordTrigger
    participant T as Trigger
    KT->>T: 渲染组件，传递 popupMotion { motionName: transitionName }

Loading

Poem

我是一只快乐的小兔子，
在代码森林里欢快跳跃，
依赖升级如春风拂面，
动画传参焕然一新，
我的步伐轻盈，散播修改的诗篇 🐇✨
让每一行代码都跳跃着欢颜。

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/KeywordTrigger.tsx

Oops! Something went wrong! :(

ESLint: 7.32.0

ESLint couldn't find the plugin "eslint-plugin-react".

(The package "eslint-plugin-react" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-react@latest --save-dev

The plugin "eslint-plugin-react" was referenced from the config file in ".eslintrc.js » /node_modules/.pnpm/@umijs+fabric@3.0.0/node_modules/@umijs/fabric/dist/eslint.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2dc39f1 and 6a65d2b.

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/KeywordTrigger.tsx (1 hunks)

🔇 Additional comments (2)

package.json (1)

48-48:

❓ Verification inconclusive

验证主版本升级的兼容性影响

从 @rc-component/trigger 的 v2 升级到 v3 是一个主版本升级，可能包含破坏性更改。请确保：

1. 已经完整阅读了版本更新日志
2. 已经处理了所有的 API 变更
3. 已经完整测试了受影响的功能

---

🌐 Web query:

What are the breaking changes in @rc-component/trigger v3.0.0?

💡 Result:

The key breaking change in @rc-component/trigger v3.0.0 involves dependency migration and testing adjustments:

1. Dependency Migration
   The package now uses scoped @rc-component/* dependencies instead of legacy rc-* packages[1][8]. This requires updating imports in your project:

   - import Trigger from 'rc-trigger';
   + import Trigger from '@rc-component/trigger';

2. Testing Environment
   Added ResizeObserver mocking for Jest to handle modern browser APIs in test environments[8]. Existing tests relying on unmocked ResizeObserver behavior may need adjustments.

For full compatibility with v3.x, ensure all related rc-* dependencies (e.g., rc-align, rc-motion) are replaced with their @rc-component equivalents[8].

Citations:

• 1: https://www.npmjs.com/package/@rc-component/trigger
• 2: https://nextjs.org/blog/next-15-rc2
• 3: https://coil-kt.github.io/coil/changelog/
• 4: https://grafana.com/docs/loki/latest/setup/upgrade/
• 5: https://ru.react.dev/blog/2024/04/25/react-19-upgrade-guide
• 6: https://community.redwoodjs.com/t/redwood-v3-0-0-rc-is-now-available/3836
• 7: https://pyquil-docs.rigetti.com/en/stable/changes.html
• 8: https://github.com/react-component/trigger/releases
• 9: https://mudblazor.com/mud/project/releases
• 10: https://react-spectrum.adobe.com/releases/index.html

---

请确保完成所有必要的兼容性升级调整

当前已将 package.json 中的 "@rc-component/trigger": "^3.0.0" 升级到 v3，新版本带来了一些破坏性改动，开发者需要关注以下几点：

• 依赖迁移：新版将依赖从原先的 rc-trigger 迁移为 @rc-component/trigger。请检查项目中所有使用该库的导入语句，确保将诸如

  - import Trigger from 'rc-trigger';
  + import Trigger from '@rc-component/trigger';

  更新为新的包名。

• 测试环境调整：v3 版本引入了 ResizeObserver 的模拟支持。请确认测试代码已相应调整，确保 Jest 或其他测试工具中已正确配置 ResizeObserver 的模拟，否则可能导致部分测试失败。

• 操作建议：

  • 阅读 @rc-component/trigger v3.0.0 的更新日志，详细了解所有破坏性变更。
  • 对受影响功能进行全面测试，确保 API 调整及环境配置的兼容性。

src/KeywordTrigger.tsx (1)

91-91: 符合新版本 API 规范的更改

将 popupTransitionName 更改为 popupMotion={{ motionName: transitionName }} 的修改正确符合了 @rc-component/trigger v3 的新 API 规范。

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@rc-component/trigger@3.1.0 🔁 npm/@rc-component/trigger@1.18.3, npm/@rc-component/trigger@2.2.6	None	+2	224 kB	zombiej

View full report↗︎

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.39%. Comparing base (2dc39f1) to head (6a65d2b).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #287   +/-   ##
=======================================
  Coverage   98.39%   98.39%           
=======================================
  Files           7        7           
  Lines         249      249           
  Branches       59       59           
=======================================
  Hits          245      245           
  Misses          4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.