fix(bundler-mako): analyze don't work in umi

[sorrycc]

Close #1364

Summary by CodeRabbit

• 新功能

  • 生成的分析报告文件名更改为 analyze-report.html，更加清晰明了。
  • 增加生成分析报告路径的打印信息，方便用户查看报告文件位置。

• 改进

  • 在编译器实现中，分析信息写入操作不再依赖配置条件，确保在特定操作后无条件执行。

• 配置管理

  • checkConfig 函数中删除了 config.analyze 的风险检查。
  • getMakoConfig 函数中增加了 analyze 配置项，支持基于环境变量 ANALYZE 设置。

[coderabbitai]

Walkthrough

本次变更主要涉及优化 analyze 报告的生成路径和文件命名，提高代码日志的明确性，以及修复 bundler-mako 包中 analyze 功能无法启用的问题。通过这些调整，确保当配置 analyze 功能时，能够正常生成分析报告，并在控制台输出生成路径。

Changes

文件路径	变更摘要
crates/mako/src/generate/analyze.rs	更新 analyze 报告的生成路径、文件命名和增加日志打印路径。
crates/mako/src/generate/mod.rs	逻辑调整，将分析信息写入操作移动到代码中的不同位置，不再依赖于配置存在。
packages/bundler-mako/index.js	移除 analyze 字段对配置检查的限制，确保从环境变量设置 analyze 配置。

Sequence Diagram(s)

不适用，本次变更中没有涉及复杂的新特性或控制流程的修改。

Assessment against linked issues

Objective	Addressed	Explanation
修复 analyze 功能无法启用的问题 (#1364)	✅

Poem

🐰 在代码的丛林中，
改进分析报告名，
日志里路径显现清，
analyze 功能重新开。
调整配置一瞬间，
兔子笑颜一整天。 🌟

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 62e1227 and babd97a.

Files selected for processing (3)

• crates/mako/src/generate/analyze.rs (1 hunks)
• crates/mako/src/generate/mod.rs (2 hunks)
• packages/bundler-mako/index.js (3 hunks)

Files skipped from review due to trivial changes (1)

• crates/mako/src/generate/mod.rs

Additional comments not posted (5)

crates/mako/src/generate/analyze.rs (3)

34-34: 更改报告文件名以提高清晰度

将报告文件名从 report.html 更改为 analyze-report.html 有助于更好地理解报告的用途。

---

35-35: 使用引用提高代码清晰度

在 fs::write 函数中使用引用以提高代码的清晰度和一致性。

---

36-39: 添加打印语句以显示生成的报告路径

添加打印语句可以帮助调试和验证报告生成路径。

packages/bundler-mako/index.js (2)

Line range hint 93-93:
更新 checkConfig 函数以支持 analyze 配置

checkConfig 函数不再将 'config.analyze' 视为风险项，表明 analyze 配置现在被认为是稳定和受支持的。

---

443-443: 更新 getMakoConfig 函数以处理 analyze 配置

getMakoConfig 函数现在在解构 opts.config 时包含 analyze，并根据 process.env.ANALYZE 环境变量设置 analyze。此更改确保 analyze 配置得到正确处理，并且可以通过环境变量进行控制。

Also applies to: 609-609