chore: 增加 useHtmlComponents 模式

[xiaoyatong]

🤔 这个变动的性质是？

• 新特性提交
• 日常 bug 修复
• 站点、文档改进
• 演示代码改进
• 组件样式/交互改进
• TypeScript 定义更新
• 包体积优化
• 性能优化
• 功能增强
• 国际化改进
• 重构
• 代码风格优化
• 测试用例
• 分支合并
• 其他改动（是关于什么的改动？）

🔗 相关 Issue

💡 需求背景和解决方案

☑️ 请求合并前的自查清单

⚠️ 请自检并全部勾选全部选项。⚠️

• 文档已补充或无须补充
• 代码演示已提供或无须提供
• TypeScript 定义已补充或无须补充
• fork仓库代码是否为最新避免文件冲突
• Files changed 没有 package.json lock 等无关文件

Summary by CodeRabbit

• 新特性
  • 新增开发命令，可在开发时启用 HTML 构建模式，提升调试与预览体验。
  • 支持根据环境变量自动调整 H5 构建配置，增加构建过程的灵活性。

[coderabbitai]

Walkthrough

本次变更在两个位置引入了对环境变量 USE_HTML 的支持。首先，package.json 中新增了脚本 "dev:taro:h5:html"，在执行开发命令前设置 USE_HTML=1。随后，在 packages/nutui-taro-demo/config/index.js 中，根据 USE_HTML 的值设置了 h5 配置对象的 useHtmlComponents 属性，并添加了日志记录。这些改动使得在 Taro 的 H5 构建过程中，可以根据环境变量灵活地启用 HTML 组件。

Changes

文件	变更描述
package.json	新增脚本 "dev:taro:h5:html": "USE_HTML=1 pnpm dev:taro h5"
packages/.../config/index.js	根据 USE_HTML 环境变量设置 h5 配置对象中的 useHtmlComponents 属性，并添加日志记录

Sequence Diagram(s)

sequenceDiagram
    participant 开发者
    participant Shell
    participant Taro
    participant Config

    开发者->>Shell: 执行脚本 dev:taro:h5:html
    Shell->>Taro: 设置环境变量 USE_HTML=1 并启动命令
    Taro->>Config: 加载配置文件
    Config->>Taro: 读取 USE_HTML 并确定 useHtmlComponents 值
    Taro->>Shell: 返回运行结果

Loading

Possibly related PRs

• chore: support pnpm workspace #2842: 此 PR 也对 package.json 中的环境变量处理及开发命令做了相关调整。
• chore: show unadapted components for HarmonyOS in Mini Programs and H5 #2999: 该变更涉及 package.json 环境变量设置，与本次对 USE_HTML 环境变量的支持具有代码层面的联系。

Suggested reviewers

• xiaoyatong
• Alex-huxiyang

Poem

嗨，我是小兔子，跳跃在代码林间，
环境变量闪耀着新的光芒，
在 package.json 中种下希望，
在 config 里记录着变更的足迹，
H5 构建如春日花开，兔步轻盈迎曙光！ 🐇✨

---

📜 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 5754750 and 9e989ad.

📒 Files selected for processing (1)

• package.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test

---

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

🪧 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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 87.20%. Comparing base (abd2516) to head (9e989ad).
Report is 1 commits behind head on feat_v3.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           feat_v3.x    #3156   +/-   ##
==========================================
  Coverage      87.20%   87.20%           
==========================================
  Files            279      279           
  Lines          18538    18538           
  Branches        2822     2822           
==========================================
  Hits           16166    16166           
  Misses          2367     2367           
  Partials           5        5           

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