chore: Add publish file

[originalix]

Summary by CodeRabbit

• 新功能
  • 更新了 package.json 文件，允许将 third-party 目录中的所有文件包含在包分发中。
• 脚本修改
  • 修改了 coverage 脚本，排除了 third-party/** 目录的覆盖检查。

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[coderabbitai]

Walkthrough

package.json 文件已更新，新增 "third-party/**" 进入 files 数组，以便将 third-party 目录中的所有文件包含在包的分发中。同时，coverage 脚本也进行了修改，排除了 third-party/** 目录的覆盖检查。其他部分未做更改。

Changes

文件	变更摘要
package.json	添加 "third-party/**" 到 files 数组；修改 coverage 脚本以排除 third-party/** 目录。

---

🪧 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 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 or 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range comments (1)

package.json (1)

Line range hint 45-45: 确认测试覆盖率的合理性

排除第三方代码的测试覆盖率检查是合理的，但建议：

1. 在文档中说明为什么排除这些文件
2. 考虑为第三方代码添加基本的集成测试

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 4a5219f and f9f1439.

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (2)

package.json (2)

33-34: 验证第三方代码处理的一致性

很好！配置文件在处理第三方代码时保持了一致性：

• files 数组包含了 third-party/**
• coverage 脚本排除了 third-party/**
• standard.ignore 也排除了 third-party/**

Also applies to: 45-45, 89-91

---

33-34: 🧹 Nitpick (assertive)

检查第三方代码的许可证和安全性

将整个 third-party 目录添加到发布文件中可能会带来潜在风险。建议：

1. 确保所有第三方代码都有明确的许可证
2. 仔细审查第三方代码的安全性
3. 考虑只包含必要的第三方文件，而不是整个目录