Skip to content

fix(taro-platform-h5): 修复生成definition.json api为空,导致Taro.xxx未能被转换 #17543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2025

Conversation

Single-Dancer
Copy link
Collaborator

@Single-Dancer Single-Dancer commented Apr 14, 2025

ref: #17480 (comment)

这个 PR 做了什么? (简要描述所做更改)
修复了 Taro.xxx 等api在h5平台undefined。原因是生成的definition.json的api为空,而definition.json的内容会被作为参数传递给babel插件babel-plugin-transform-taroapi,将 Taro.xxx 写法转换为 import { xxx } from '@tarojs/taro'。由于为空,所以无法得到转换,导致调用 Taro.xxx 会报错。

这个 PR 是什么类型? (至少选择一个)

  • 错误修复(Bugfix) issue: fix #
  • 新功能(Feature)
  • 代码重构(Refactor)
  • TypeScript 类型定义修改(Typings)
  • 文档修改(Docs)
  • 代码风格更新(Code style update)
  • 其他,请描述(Other, please describe):

这个 PR 涉及以下平台:

  • 所有小程序
  • 微信小程序
  • 支付宝小程序
  • 百度小程序
  • 字节跳动小程序
  • QQ 轻应用
  • 京东小程序
  • 快应用平台(QuickApp)
  • Web 平台(H5)
  • 移动端(React-Native)
  • 鸿蒙(harmony)

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores
    • 更新了 API 定义解析的默认配置,以支持 ECMAScript 模块,提高了模块兼容性。
    • 修改了 GitHub Actions 工作流中的测试作业名称,并更新了覆盖率报告上传步骤的参数。
    • 更新了多个包的开发依赖,替换了 TypeScript 插件以优化构建过程。

@Single-Dancer Single-Dancer requested a review from tutuxxx April 14, 2025 07:50
Copy link

coderabbitai bot commented Apr 14, 2025

Walkthrough

此次更改更新了 parseDefinitionJSON 方法中 apisPath 参数的默认值,将原先指向 @tarojs/taro-h5/dist/index.d.ts 的路径修改为指向 @tarojs/taro-h5/dist/index.esm.d.ts。此外,GitHub Actions 工作流中的 Node.js 测试作业名称也被更改,并对多个步骤的参数进行了更新。同时,多个 package.json 文件中的开发依赖项进行了调整,主要是将 @rollup/plugin-typescript 替换为 rollup-plugin-ts,并对 Rollup 配置文件进行了相应的修改。

Changes

文件路径 变更摘要
packages/taro-platform-h5/build/definition-json/parser.ts 更新 parseDefinitionJSON 方法中 apisPath 默认值,从 index.d.ts 改为 index.esm.d.ts
.github/workflows/nodejs.yml 更改作业名称为 nodejs-tesing,并在上传覆盖率报告的步骤中添加 move_coverage_to_trash: true 参数
packages/taro-h5/package.json 更新构建和测试脚本,修改 rollup 脚本使用 rollup.config.mts,并直接引用 Jest 二进制文件
packages/taro-h5/rollup.config.mts 将 TypeScript 插件从 @rollup/plugin-typescript 更改为 rollup-plugin-ts,并更新配置以生成源映射
packages/taro-h5/tsconfig.json sourceMap 选项从 true 改为 false,并更新 include 数组以使用 rollup.config.mts
packages/taro-platform-harmony-hybrid/package.json 降级 @rollup/plugin-typescript 版本并添加 rollup-plugin-ts 依赖项
packages/taro-platform-harmony-hybrid/rollup.config.ts 将 TypeScript 插件更改为 rollup-plugin-ts,并更新输入路径以使用动态路径构造
packages/taro-platform-harmony-hybrid/tsconfig.json 移除 declarationoutDir 选项
packages/taro-platform-harmony/package.json 移除 @rollup/plugin-typescript 依赖并添加 rollup-plugin-ts 依赖
packages/taro-platform-harmony/rollup.config.ts 更新 Rollup 配置,使用 rollup-plugin-ts,并更新输入和输出路径
packages/taro-router/package.json types 属性更改为 typings,并更新路径为 dist/index.esm.d.ts
packages/taro-runtime/package.json 移除 @rollup/plugin-typescript 依赖并添加 rollup-plugin-ts 依赖
packages/taro-runtime/rollup.config.ts 将 TypeScript 插件更改为 rollup-plugin-ts,并简化配置

Poem

我是小兔来报好消息,
代码里跳跃着新节奏🐰,
参数更新悄然无声,
ECMAScript 模块迎风而动,
轻轻一变展未来新梦。

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
✨ Finishing Touches
  • 📝 Generate Docstrings

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

@Single-Dancer Single-Dancer requested a review from yoyo837 April 14, 2025 07:50
@Single-Dancer Single-Dancer added this to the 4.0.11 milestone Apr 14, 2025
@yoyo837
Copy link
Contributor

yoyo837 commented Apr 14, 2025

@ianzone

@Single-Dancer
Copy link
Collaborator Author

我还是先revert吧,看着还有snap文件的变动之类的

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ada3c68 and 1218941.

⛔ Files ignored due to path filters (2)
  • packages/babel-plugin-transform-taroapi/__tests__/__snapshots__/index.spec.ts.snap is excluded by !**/*.snap
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (13)
  • .github/workflows/nodejs.yml (2 hunks)
  • packages/taro-h5/package.json (2 hunks)
  • packages/taro-h5/rollup.config.mts (2 hunks)
  • packages/taro-h5/tsconfig.json (1 hunks)
  • packages/taro-platform-h5/build/definition-json/parser.ts (1 hunks)
  • packages/taro-platform-harmony-hybrid/package.json (1 hunks)
  • packages/taro-platform-harmony-hybrid/rollup.config.ts (4 hunks)
  • packages/taro-platform-harmony-hybrid/tsconfig.json (1 hunks)
  • packages/taro-platform-harmony/package.json (1 hunks)
  • packages/taro-platform-harmony/rollup.config.ts (6 hunks)
  • packages/taro-router/package.json (1 hunks)
  • packages/taro-runtime/package.json (2 hunks)
  • packages/taro-runtime/rollup.config.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/taro-platform-h5/build/definition-json/parser.ts
🧰 Additional context used
🧬 Code Graph Analysis (2)
packages/taro-platform-harmony-hybrid/rollup.config.ts (1)
packages/taro-framework-vue3/rollup.config.js (1)
  • cwd (8-8)
packages/taro-platform-harmony/rollup.config.ts (1)
packages/taro-framework-vue3/rollup.config.js (1)
  • cwd (8-8)
🪛 actionlint (1.7.4)
.github/workflows/nodejs.yml

121-121: input "move_coverage_to_trash" is not defined in action "codecov/codecov-action@v4". available inputs are "codecov_yml_path", "commit_parent", "directory", "disable_file_fixes", "disable_safe_directory", "disable_search", "dry_run", "env_vars", "exclude", "fail_ci_if_error", "file", "files", "flags", "git_service", "handle_no_reports_found", "job_code", "name", "network_filter", "network_prefix", "os", "override_branch", "override_build", "override_build_url", "override_commit", "override_pr", "plugin", "plugins", "report_code", "root_dir", "slug", "token", "url", "use_legacy_upload_endpoint", "use_oidc", "verbose", "version", "working-directory"

(action)


129-129: input "move_coverage_to_trash" is not defined in action "codecov/codecov-action@v4". available inputs are "codecov_yml_path", "commit_parent", "directory", "disable_file_fixes", "disable_safe_directory", "disable_search", "dry_run", "env_vars", "exclude", "fail_ci_if_error", "file", "files", "flags", "git_service", "handle_no_reports_found", "job_code", "name", "network_filter", "network_prefix", "os", "override_branch", "override_build", "override_build_url", "override_commit", "override_pr", "plugin", "plugins", "report_code", "root_dir", "slug", "token", "url", "use_legacy_upload_endpoint", "use_oidc", "verbose", "version", "working-directory"

(action)


137-137: input "move_coverage_to_trash" is not defined in action "codecov/codecov-action@v4". available inputs are "codecov_yml_path", "commit_parent", "directory", "disable_file_fixes", "disable_safe_directory", "disable_search", "dry_run", "env_vars", "exclude", "fail_ci_if_error", "file", "files", "flags", "git_service", "handle_no_reports_found", "job_code", "name", "network_filter", "network_prefix", "os", "override_branch", "override_build", "override_build_url", "override_commit", "override_pr", "plugin", "plugins", "report_code", "root_dir", "slug", "token", "url", "use_legacy_upload_endpoint", "use_oidc", "verbose", "version", "working-directory"

(action)


145-145: input "move_coverage_to_trash" is not defined in action "codecov/codecov-action@v4". available inputs are "codecov_yml_path", "commit_parent", "directory", "disable_file_fixes", "disable_safe_directory", "disable_search", "dry_run", "env_vars", "exclude", "fail_ci_if_error", "file", "files", "flags", "git_service", "handle_no_reports_found", "job_code", "name", "network_filter", "network_prefix", "os", "override_branch", "override_build", "override_build_url", "override_commit", "override_pr", "plugin", "plugins", "report_code", "root_dir", "slug", "token", "url", "use_legacy_upload_endpoint", "use_oidc", "verbose", "version", "working-directory"

(action)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
  • GitHub Check: Build Rust Binding / stable - aarch64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
  • GitHub Check: Build Rust Binding / stable - x86_64-apple-darwin
🔇 Additional comments (26)
packages/taro-platform-harmony-hybrid/tsconfig.json (1)

9-9: 保留调试选项及简化配置
此处明确配置 "sourceMap": true 保留了调试信息,同时移除了不再需要的 "declaration""outDir" 配置。请确认这一更改符合整体构建和发布策略。

packages/taro-h5/tsconfig.json (2)

8-8: 关闭 sourceMap 生成
"sourceMap" 修改为 false 意味着不生成 source map 文件,请确保这不会影响 H5 调试和错误追踪。


10-10: 更新 Rollup 配置文件路径
"include" 数组中将 rollup.config.ts 替换为 rollup.config.mts,确保构建流程加载的是新的模块格式配置文件。

packages/taro-router/package.json (1)

11-11: 更新声明文件属性
将原先的 "types": "dist/index.d.ts" 替换为 "typings": "dist/index.esm.d.ts",这有助于保持与 ECMAScript 模块格式的一致性。请确认对外接口引用时使用正确的声明文件。

packages/taro-platform-harmony/package.json (1)

50-50: 切换 Rollup TypeScript 插件
使用 "rollup-plugin-ts": "^3.4.5" 替换旧版的插件配置,有助于改进 TypeScript 的构建流程。建议确认该插件的配置与整个构建系统保持一致。

packages/taro-platform-harmony-hybrid/package.json (2)

63-63: 降级 @rollup/plugin-typescript 版本
"@rollup/plugin-typescript" 版本从之前的较高版本调整为 ^11.1.0,此调整可能是为了提高构建稳定性,请核实新版插件在所有构建场景下均能正常工作。


70-70: 新增 rollup-plugin-ts 依赖
添加 "rollup-plugin-ts": "^3.4.5" 以与其他包保持一致,帮助优化 TypeScript 文件的 Rollup 构建流程。

packages/taro-h5/package.json (3)

26-26: 变更 Rollup 配置文件格式

将 Rollup 配置从 .ts 更改为 .mts 并添加了 --bundleConfigAsCjs 标志。这个更改使得配置文件采用 ES 模块格式,同时确保输出兼容 CommonJS。这是一个正向的改进,更符合现代 JavaScript 模块化标准。


27-27: 更新测试脚本路径

将测试命令从简单的 jest 更改为直接引用 node_modules/jest/bin/jest.js。这种做法可以确保使用当前项目依赖中的 Jest 版本,避免全局安装的 Jest 可能带来的版本不一致问题。


73-73: 更换 TypeScript 插件

@rollup/plugin-typescript 替换为 rollup-plugin-ts。这个变更是整个 PR 中一系列插件更换的一部分,目的可能是为了更好的 TypeScript 支持或构建性能。

这个改动应该与第 26 行的 Rollup 配置文件变更保持一致,确保插件能够正确加载和使用。

packages/taro-runtime/rollup.config.ts (2)

4-4: 更新 TypeScript 插件导入

@rollup/plugin-typescript 替换为 rollup-plugin-ts。这与 package.json 中的依赖变更保持一致,是整个项目构建系统更新的一部分。


16-16: 简化 TypeScript 插件配置

移除了原有 TypeScript 插件的配置选项,使用更简洁的方式初始化 ts 插件。这表明 rollup-plugin-ts 可能具有更好的默认配置,减少了样板代码,简化了维护工作。

.github/workflows/nodejs.yml (1)

121-121:

❓ Verification inconclusive

检查 Codecov 行为的参数有效性

添加了 move_coverage_to_trash: true 参数到 Codecov 行为中。虽然这个参数的目的可能是清理已处理的覆盖率文件以避免工作空间混乱,但静态分析显示 move_coverage_to_trash 不是 codecov/codecov-action@v4 的定义输入。这可能导致工作流运行时出现问题。

建议验证此参数的有效性,或者检查 Codecov 文档以找到正确的参数名称。

Also applies to: 129-129, 137-137, 145-145


🏁 Script executed:

#!/bin/bash
# 查询 codecov-action 的最新文档,验证参数有效性
curl -s https://raw.githubusercontent.com/codecov/codecov-action/master/action.yml | grep -A 2 "move_coverage_to_trash"

Length of output: 119


验证 Codecov Action 输入参数 move_coverage_to_trash 的有效性

目前通过自动查询 Codecov Action 的定义文件未能检索到 move_coverage_to_trash 参数,建议您手动查阅 Codecov 官方文档确认该参数是否被支持。如果确认该参数不再有效或未被定义,请在工作流程配置中删除或修正对应设置,以免影响 workflow 的正常运行。

  • 涉及文件:.github/workflows/nodejs.yml
  • 相关行:121, 129, 137, 145
🧰 Tools
🪛 actionlint (1.7.4)

121-121: input "move_coverage_to_trash" is not defined in action "codecov/codecov-action@v4". available inputs are "codecov_yml_path", "commit_parent", "directory", "disable_file_fixes", "disable_safe_directory", "disable_search", "dry_run", "env_vars", "exclude", "fail_ci_if_error", "file", "files", "flags", "git_service", "handle_no_reports_found", "job_code", "name", "network_filter", "network_prefix", "os", "override_branch", "override_build", "override_build_url", "override_commit", "override_pr", "plugin", "plugins", "report_code", "root_dir", "slug", "token", "url", "use_legacy_upload_endpoint", "use_oidc", "verbose", "version", "working-directory"

(action)

packages/taro-runtime/package.json (2)

22-22: 指定 Rollup 配置插件

保留了 .ts 扩展名的 Rollup 配置文件,但明确指定了 --configPlugin typescript。这确保了使用正确的插件来处理配置文件,与项目中其他包采用的 .mts 方式略有不同,但功能上应该是一致的。


43-43: 更新 TypeScript 插件依赖

@rollup/plugin-typescript 替换为 rollup-plugin-ts,与 rollup 配置文件中的导入保持一致。这是整个项目构建系统更新的一部分,目的是使用更现代的 TypeScript 处理方式。

确保这个变更在所有相关文件中都保持一致,以避免构建过程中的兼容性问题。

packages/taro-h5/rollup.config.mts (2)

7-7: 改进了依赖项管理

@rollup/plugin-typescript 切换到 rollup-plugin-ts 是一项很好的改进,这与PR中其他文件的更改保持一致。rollup-plugin-ts 提供了更好的TypeScript支持和更灵活的配置选项。


27-30:

✅ Verification successful

配置优化,启用了源映射

通过添加 tsconfig 函数并设置 sourceMap: true,改进了TypeScript编译配置。这将有助于调试,并且可能与修复API定义问题有间接关系,因为更好的类型处理可能会影响最终生成的定义文件。


🏁 Script executed:

#!/bin/bash
# 检查TypeScript相关包的版本和依赖关系
grep -r "rollup-plugin-ts\|@rollup/plugin-typescript" --include="package.json" .

Length of output: 2547


配置优化验证通过:已正确启用 SourceMap

packages/taro-h5/rollup.config.mts 中,通过如下配置:

tsconfig: (e) => ({
  ...e,
  sourceMap: true,
}),

实现了合并原有 tsconfig 设置并启用 sourceMap,从而提高了调试体验,并可能间接改善 API 定义问题。同时,根据检查依赖包版本的信息,rollup-plugin-ts@rollup/plugin-typescript 均处于符合要求的版本范围。

packages/taro-platform-harmony-hybrid/rollup.config.ts (5)

1-2: 添加了必要的路径模块和更新了TS插件

添加了path模块导入并更换了TypeScript插件,这是一个合理的改进。使用rollup-plugin-ts可以提供更强大的TypeScript处理能力,这可能与修复API定义问题有关。

Also applies to: 9-9


15-16: 添加了当前工作目录常量

添加cwd常量用于后续路径解析是一个良好的实践,这样可以确保无论从哪里执行构建脚本,路径都能正确解析。这与其他文件中的做法保持一致。


37-43: 改进了TypeScript编译配置

通过使用tsconfig函数并启用declarationsourceMap选项,改进了TypeScript编译配置。设置declaration: true对于生成类型声明文件很重要,这可能与修复API定义问题直接相关,因为API定义可能依赖于这些生成的声明文件。


91-91: 使用动态路径解析导出插件

rollup-plugin-export-name-only.js使用动态路径是个好习惯,提高了代码的可维护性。这个插件可能与处理API导出名称有关,可能与修复API定义问题相关。


80-80:

✅ Verification successful

使用动态路径解析

使用path.join(cwd, 'src/runtime/apis/index.ts')替代硬编码路径,提高了代码的可维护性和跨平台兼容性。这个文件看起来与Taro API转换直接相关,注释中提到"供 babel-plugin-transform-taroapi 使用",这可能是修复PR中提到的API问题的关键部分。


🏁 Script executed:

#!/bin/bash
# 检查taroApis.js的输出和相关配置
grep -r "babel-plugin-transform-taroapi" --include="*.json" --include="*.js" --include="*.ts" .

Length of output: 1747


确认动态路径解析实现符合要求
经过验证,项目中与 babel-plugin-transform-taroapi 相关的多个模块都已正确使用动态路径解析方式(例如在 packages/taro-platform-harmony-hybrid/rollup.config.ts 第80行),此改动有效提升了代码的可维护性和跨平台兼容性,同时确保了 tree-shaking 功能不受影响。此次修改也验证了 PR 中对 API 问题修复的有效性,请继续关注相关测试,以确保整体稳定性。

packages/taro-platform-harmony/rollup.config.ts (4)

1-2: 添加了路径模块和更新了TS插件

添加了join函数导入,切换到rollup-plugin-ts插件,并定义了cwd常量。这些更改与其他文件保持一致,是对构建配置的良好改进。使用当前目录作为基础路径可以确保跨平台构建的一致性。

Also applies to: 8-9, 10-10


23-29: 优化了TypeScript编译配置

通过配置declaration: truesourceMap: true,改进了TypeScript编译设置。生成声明文件对于正确构建API定义非常重要,这可能是修复PR中描述的API问题的关键部分。


37-38: 统一使用动态路径解析

将所有输入和输出路径替换为使用join(cwd, ...)的形式,提高了代码的可维护性和跨平台兼容性。这是一个很好的改进,确保无论在哪个环境中构建项目,路径都能正确解析。

Also applies to: 39-40, 62-63, 64-65, 73-74, 75-76, 84-85, 86-87


91-96: 保持配置一致性

otherConfig中的TypeScript配置采用了相同的函数式配置方法,但保留了declaration: false,这是合理的,因为这些组件文件可能不需要生成声明文件。这保持了整个配置的一致性和可维护性。

@@ -28,7 +28,7 @@ jobs:
name: Build Rust WASM
uses: ./.github/workflows/build-rust-wasm.yml

nodejs-testing:
nodejs-tesing:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

修复 Job 名称拼写错误

当前的 Job 名称 nodejs-tesing 缺少一个字母 't',应该是 nodejs-testing。这个拼写错误应该被更正,以保持命名一致性。

-  nodejs-tesing:
+  nodejs-testing:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
nodejs-tesing:
nodejs-testing:

Copy link

codecov bot commented Apr 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.37%. Comparing base (5e4de56) to head (1218941).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #17543      +/-   ##
==========================================
+ Coverage   57.70%   58.37%   +0.67%     
==========================================
  Files         469      469              
  Lines       26551    27231     +680     
  Branches     5872     6000     +128     
==========================================
+ Hits        15321    15896     +575     
- Misses       9768     9805      +37     
- Partials     1462     1530      +68     
Flag Coverage Δ
taro-cli 72.37% <ø> (ø)
taro-runtime 59.87% <ø> (ø)
taro-web 52.75% <ø> (+3.08%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 185 files with indirect coverage changes

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

@Single-Dancer Single-Dancer merged commit b8f0e34 into main Apr 14, 2025
39 checks passed
@Single-Dancer Single-Dancer deleted the fix/h5-api branch April 14, 2025 08:38
@Single-Dancer Single-Dancer modified the milestones: 4.0.11, 4.0.12 Apr 14, 2025
ianzone added a commit to ianzone/taro that referenced this pull request Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants