fix: 类型构建错误

[oasis-cloud]

Summary by CodeRabbit

• 新功能
  • 更新了TypeScript声明文件的输出路径结构，以适应新的目录组织。
• 修复
  • 取消删除已读取的声明文件，确保文件在构建过程中保留。

[coderabbitai]

Walkthrough

此次更改涉及 vite.config.build.taro.ts 和 vite.config.build.ts 文件中的 TypeScript 声明文件路径处理逻辑。具体来说，输出文件的路径构造方式进行了调整，之前的路径替换逻辑已被修改，以适应新的目录结构。这些更改将影响生成的 TypeScript 定义文件的模块解析和导入方式。

Changes

文件	更改摘要
vite.config.build.taro.ts, vite.config.build.ts	修改了 TypeScript 声明文件的路径处理逻辑，调整了输出目录结构，取消了删除某些文件的操作。

Suggested labels

size/XXL

🐇 在代码的草地上跳跃，
路径新生，变化无穷，
文件不再被遗忘，
结构清晰如晨曦，
兔子欢跃，庆新生！ 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6b87265 and 2e98a84.

Files selected for processing (2)

• vite.config.build.taro.ts (1 hunks)
• vite.config.build.ts (1 hunks)

Additional comments not posted (3)

vite.config.build.ts (2)

46-46: 请确认是否有意注释掉删除类型定义文件的代码。

注释掉 fse.remove('./dist/types/packages/nutui.react.build.d.ts') 这行代码意味着在读取该文件后不会删除它。请确认这是否是有意为之，并确保正确管理和更新类型定义文件，以避免过时或陈旧的类型定义。

---

49-49: 请验证新的路径结构是否正确，并评估其对模块解析和导入的影响。

将类型声明文件中的 ./ 替换为 ./packages/ 表明输出文件 ./dist/types/index.d.ts 中的路径结构发生了变化。请确保新的路径结构与实际的包组织相一致，不会破坏任何现有的导入。建议进行以下验证：

vite.config.build.taro.ts (1)

50-50: 调整了生成的 TypeScript 声明文件中的路径处理逻辑

这个变更修改了在生成 TypeScript 声明文件时，文件路径的构造方式。具体来说：

• 之前的代码将生成的声明文件中的 ../ 替换为 ./，这可能是为了调整输出文件的相对路径。
• 更新后的代码现在将 ./ 替换为 ./packages/，表明输出文件所在的目录结构发生了变化。

这一改动表明输出目录结构进行了重组，可能是为了更好地与新的打包或模块系统保持一致。

这个变更会影响输出文件路径的解析方式，进而可能影响生成的 TypeScript 定义中的模块解析和导入。这一改动非常重要，因为它修改了路径处理的逻辑，而这对于确保生成的类型在应用的其他部分中被正确引用至关重要。

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.11%. Comparing base (6b87265) to head (2e98a84).
Report is 1 commits behind head on next.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #2605   +/-   ##
=======================================
  Coverage   83.11%   83.11%           
=======================================
  Files         218      218           
  Lines       17817    17817           
  Branches     2545     2545           
=======================================
  Hits        14809    14809           
  Misses       3003     3003           
  Partials        5        5           

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