Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Bundling should allow to mark input bundles as "do not resolve"

未关闭
#351 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
build-system

调研方向

Start with the bundle definition handling and the module-existence logic in lib/lbt/bundle/Resolver.js, especially lines 63-78. Reproduce the issue by bundling sap/viz/ and inspect the resolver output. Done means an input bundle can be explicitly marked not to dissolve, the build remains functional, and the spurious missing-module errors no longer appear.

由索引模型根据 Issue 内容生成。

描述

module/ui5-builder

Expected Behavior

Bundling should allow to specify an input source file as "bundle that must not be dissolved into pieces" and rather embed the input source as a whole.

Current Behavior

When a bundle is created that includes e.g. one of the sap-viz-* bundles, the builder logs many errors like

ERR! lbt:bundle:Resolver **** error: missing module sap/viz/framework/common/util/NameColorUtils.js, required by sap/viz/libs/sap-viz-info-charts.js

The resulting bundle works, but the log messages are annoying. And the current logic that checks for any module to exist might lead to unexpected behavior. It might be better to mark the input bundle explicitly as "do not dissolve".

Steps to reproduce the issue

  1. Create a bundle definition that includes sap/viz/
  2. Build the bundle
  3. Watch the console output

Affected components (if known)

主要语言
JavaScript
星标
511
派生
83
平均合并
1 天 3 小时
30 天内合并 PR
54

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

UI5/cli 的其他 Issue

查看 UI5/cli 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。