chore: fix alias for docs demos

[aojunhao123]

Summary by CodeRabbit

发布说明

• 重构
  • 更新了模块解析配置，优化了内部依赖管理
  • 简化了示例文件的外部依赖

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

[vercel]

@aojunhao123 is attempting to deploy a commit to the React Component Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

概览

拉取请求对项目的模块解析配置和导入进行了调整。更新了 Dumi 配置中的路径别名以指向本地源目录，修正了 TypeScript 配置中的路径映射文件扩展名，并移除了示例文件中的 CSS 导入。

变更

文件群组 / 文件	变更摘要
配置文件更新 \.dumirc.ts, tsconfig.json	更新模块解析配置。.dumirc.ts 中添加 path 导入和 alias 属性，将 'rc-util/es' 映射至本地 src 目录。tsconfig.json 中将 "rc-util" 路径别名的目标从 "src/index.tsx" 更改为 "src/index.ts"。
示例文件清理 docs/examples/focus.tsx	移除 focus.css 样式表导入，简化文件依赖而不改变核心逻辑。

预估代码审查工作量

🎯 2 (简单) | ⏱️ ~8 分钟

需要特别关注的事项：

• 验证 .dumirc.ts 中新的 alias 配置与 Dumi 版本的兼容性
• 确认 tsconfig.json 中路径映射从 .tsx 更改为 .ts 不会导致类型解析问题
• 检查移除 focus.css 导入后示例是否正常渲染

诗

🐰 配置轻轻来调整，
路径别名指向新方向，
CSS 导入已卸下，
整洁如初绽新颜，
模块解析更通达！✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	PR 标题准确概括了主要变更：在 .dumirc.ts 中修复文档演示的别名配置，同时在 tsconfig.json 中更新了路径映射。
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 7e344f2 and 0e221b6.

📒 Files selected for processing (3)

• .dumirc.ts (2 hunks)
• docs/examples/focus.tsx (0 hunks)
• tsconfig.json (1 hunks)

💤 Files with no reviewable changes (1)

• docs/examples/focus.tsx

🔇 Additional comments (3)

.dumirc.ts (2)

3-3: 正确导入 path 模块。

添加 path 模块导入是必要的，用于在 alias 配置中使用 path.resolve()。

---

18-20: 验证 Dumi alias 配置的有效性。

新增的 alias 配置将 'rc-util/es' 映射到本地 src 目录，这与 tsconfig.json 中的路径配置保持一致。请验证该配置在 Dumi 中能正常工作，并确保文档演示能正确解析模块路径。

建议在本地测试文档演示，确认模块解析问题已修复。可以运行以下命令启动文档服务器：

#!/bin/bash
# 描述：验证Dumi配置并启动文档服务器进行测试

echo "检查Dumi版本和配置..."
npm list dumi || yarn list dumi

echo -e "\n提示：请手动运行以下命令启动文档服务器并测试："
echo "npm run dev 或 yarn dev"
echo "然后在浏览器中访问文档演示页面，验证模块导入是否正常工作"

tsconfig.json (1)

13-13: 该路径配置是正确的，无需修改。

src/index.ts 确实存在且是项目的入口文件，src/index.tsx 不存在。tsconfig.json 中将 "rc-util": ["src/index.ts"] 配置为 .ts 扩展名是正确的，不会导致模块解析失败。

Likely an incorrect or invalid review 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Summary of Changes

Hello @aojunhao123, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses module resolution issues within the documentation build system and corrects a TypeScript configuration entry. By introducing a new alias in the Dumi configuration and fixing a file extension in tsconfig.json, it ensures that documentation demos correctly locate and import rc-util modules. Additionally, a minor cleanup was performed by removing an unused CSS import from a documentation example, contributing to a more robust and accurate documentation site.

Highlights

• Dumi Configuration Update: The Dumi configuration file (.dumirc.ts) has been updated to include an alias for rc-util/es, ensuring that documentation demos correctly resolve imports from the src directory.
• TypeScript Path Correction: The tsconfig.json file was modified to correct the path for rc-util, changing it from src/index.tsx to src/index.ts for accurate module resolution.
• Documentation Example Cleanup: An unnecessary CSS import (./focus.css) was removed from the docs/examples/focus.tsx file, streamlining the demo's dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to fix aliases for documentation demos. The changes include adding a webpack alias in .dumirc.ts for rc-util/es, correcting a file path in tsconfig.json from .tsx to .ts, and removing a CSS import in a demo component. The changes are generally good and address the stated goal. I've suggested one improvement in .dumirc.ts to add another alias for rc-util to maintain consistency with the tsconfig.json paths configuration, which will make the setup more robust.

[gemini-code-assist]

For consistency with tsconfig.json, it would be beneficial to also add an alias for the root rc-util package. This ensures that all import paths are handled consistently between TypeScript's path mapping and dumi's build configuration, preventing potential resolution issues in the documentation demos.

  alias: {
    'rc-util/es': path.resolve(__dirname, 'src'),
    'rc-util$': path.resolve(__dirname, 'src/index.ts'),
  },

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.57%. Comparing base (7e344f2) to head (0e221b6).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #713   +/-   ##
=======================================
  Coverage   91.57%   91.57%           
=======================================
  Files          37       37           
  Lines         938      938           
  Branches      321      321           
=======================================
  Hits          859      859           
  Misses         77       77           
  Partials        2        2           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.