Bundling should allow to mark input bundles as "do not resolve"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 511
- Forks
- 83
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 55
Description
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
- Create a bundle definition that includes
sap/viz/ - Build the bundle
- Watch the console output
Affected components (if known)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100