chore: remove useless dependencies

[xusd320]

As title.

Summary by CodeRabbit

• 新功能

  • 引入了新的错误处理机制，改善了代码的错误报告能力。

• 代码清理

  • 移除了不必要的导入语句，提升了代码的可读性和维护性。

[coderabbitai]

Walkthrough

此次提交主要涉及对 mako crate 的多个文件进行小幅修改，包括 Cargo.toml 文件的格式调整、导入语句的更新以及未使用导入的清理。这些更改旨在优化代码结构，特别是在错误处理机制方面，尽管整体功能和逻辑未受到影响。

Changes

文件路径	更改摘要
crates/mako/Cargo.toml	对 [dev-dependencies] 部分进行了格式调整，移除了依赖声明的前导空格。
crates/mako/src/build/transform.rs	更新导入语句，添加 swc_core::base::try_with_handler，移除 swc_error_reporters::handler 的相同导入。
crates/mako/src/generate/minify.rs	更新导入语句，添加 swc_error_reporters::handler::try_with_handler，移除冗余导入。
crates/mako/src/generate/transform.rs	更新导入语句，添加 swc_core::base::try_with_handler，移除 swc_error_reporters 的相同导入。
crates/mako/src/plugins/bundless_compiler.rs	更新导入语句，添加 swc_core::base::try_with_handler，移除 swc_error_reporters 的相同导入。
crates/mako/src/generate/chunk_pot/str_impl.rs	移除未使用的导入 testing::assert_eq。

Possibly related PRs

• perf: optimize group_chunks, speed up group_chunks by 500% #1475: 修改了 Cargo.toml 文件，与主 PR 中的相同文件的更改直接相关。
• refactor: merge source map, speed up generation by 800% #1509: 也涉及 Cargo.toml 文件的更改，直接与主 PR 的依赖规范修改相关。
• revert: 1509 and 1475 #1538: 还原了 PR perf: optimize group_chunks, speed up group_chunks by 500% #1475 和 refactor: merge source map, speed up generation by 800% #1509 中的更改，与 Cargo.toml 文件的依赖管理相关。
• refactory: in str-impl chunk generate, remove cm when merge_code_and_sourcemap #1541: 涉及 crates/mako/src/generate/chunk_pot/str_impl.rs 的更改，相关于主 PR 中对 transform.rs 和 str_impl.rs 的修改。

Poem

在草地上跳跃的小兔，
依赖更新真是好事，
导入清理轻松无忧，
错误处理更显高效。
代码整洁如新装，
兔子欢跳乐无穷！ 🐇✨

Tip

OpenAI O1 model for chat

• We have deployed OpenAI's latest O1 model for chat.
• OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model.
• Please share any feedback with us in the discussions post.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e9af895 and 0a2d15f.

Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

Files selected for processing (6)

• crates/mako/Cargo.toml (1 hunks)
• crates/mako/src/build/transform.rs (1 hunks)
• crates/mako/src/generate/chunk_pot/str_impl.rs (0 hunks)
• crates/mako/src/generate/minify.rs (1 hunks)
• crates/mako/src/generate/transform.rs (1 hunks)
• crates/mako/src/plugins/bundless_compiler.rs (1 hunks)

Files not reviewed due to no reviewable changes (1)

• crates/mako/src/generate/chunk_pot/str_impl.rs

Files skipped from review due to trivial changes (2)

• crates/mako/Cargo.toml
• crates/mako/src/generate/minify.rs

Additional comments not posted (3)

crates/mako/src/plugins/bundless_compiler.rs (1)

10-10: 重构错误处理逻辑的改动看起来不错!

将 try_with_handler 的导入从 swc_error_reporters::handler 改为 swc_core::base，这表明错误处理逻辑正在重构，以利用 swc_core 库的功能。

请运行以下脚本来验证此改动对代码库中错误处理的影响:

Verification successful

---

错误处理重构已成功应用于整个代码库

验证结果显示，try_with_handler 函数的导入已在所有相关文件中从 swc_core::base 更新。这个改动已经一致地应用于 mako crate 中的多个文件，包括 bundless_compiler.rs、transform.rs、minify.rs、util.rs 和 build/transform.rs。没有发现任何遗留的旧导入。

这表明错误处理的重构已经成功完成，并且在整个代码库中保持一致。

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# 描述: 验证 `try_with_handler` 在代码库中的使用是否已更新。

# 测试: 搜索 `try_with_handler` 的使用情况。预期: 只会出现来自 `swc_core::base` 的引用。
rg --type rust $'try_with_handler'

Length of output: 960

crates/mako/src/generate/transform.rs (1)

8-8: 导入语句的修改看起来不错，但请确保新的导入提供与旧的相同的功能。

这个修改表明库的结构可能进行了重构或更新。虽然修改本身没有问题，但请验证 swc_core::base::try_with_handler 与之前的 swc_error_reporters::handler::try_with_handler 在功能上是等价的，以确保错误处理逻辑没有受到影响。

为了验证新旧导入在功能上的一致性，可以运行以下脚本:

crates/mako/src/build/transform.rs (1)

4-4: 更改符合 PR 的目标。

将 try_with_handler 的导入从 swc_error_reporters::handler 改为 swc_core::base，这与消除不必要依赖的 PR 目标一致。

请运行以下脚本来验证此更改对整体错误处理机制的影响：

Verification successful

---

导入更改已成功实施，未发现问题

经过验证，try_with_handler 的导入已在整个代码库中统一更改为 swc_core::base。这一更改在以下文件中得到了一致的实施：

• crates/mako/src/plugins/bundless_compiler.rs
• crates/mako/src/generate/transform.rs
• crates/mako/src/generate/minify.rs
• crates/mako/src/generate/chunk_pot/util.rs
• crates/mako/src/build/transform.rs

try_with_handler 的使用模式保持不变，通常与 HANDLER.set() 和 HELPERS.set() 一起使用。这表明错误处理机制的功能未受影响。

此更改似乎是更广泛重构的一部分，旨在使用 swc_core::base 替代 swc_error_reporters::handler，符合移除不必要依赖的目标。

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# 描述：验证 `try_with_handler` 在代码库中的使用是否仍然正确。

# 测试：搜索 `try_with_handler` 的使用情况。期望：`try_with_handler` 的所有使用都来自 `swc_core::base`。
rg --type rust $'try_with_handler' -A 5 

Length of output: 5711

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 62.12%. Comparing base (e9af895) to head (0a2d15f).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1595   +/-   ##
=======================================
  Coverage   62.11%   62.12%           
=======================================
  Files         129      129           
  Lines       15559    15559           
=======================================
+ Hits         9665     9666    +1     
+ Misses       5894     5893    -1     

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