|
3 | 3 | - Issue: - |
4 | 4 | - Affected components |
5 | 5 | + [X] [ui5-builder](../packages/builder) |
6 | | - + [X] [ui5-server](../packages/server) |
| 6 | + + [ ] [ui5-server](../packages/server) |
7 | 7 | + [ ] [ui5-cli](../packages/cli) |
8 | 8 | + [ ] [ui5-fs](../packages/fs) |
9 | 9 | + [X] [ui5-project](../packages/project) |
|
13 | 13 |
|
14 | 14 | ## 1. Summary |
15 | 15 |
|
16 | | -Enable seamless integration of NPM packages (ESM, CJS, and UI5 Web Components) into UI5 applications and libraries by providing a built-in standard task and middleware that automatically transforms packages from their native format to UI5's AMD module format using Rollup.js. |
| 16 | +Enable seamless integration of NPM packages (ESM, CJS, and UI5 Web Components) into UI5 applications and libraries by providing a built-in standard build task that automatically transforms packages from their native format to UI5's AMD module format using Rollup.js. |
17 | 17 |
|
18 | 18 | This RFC focuses on the implementation mechanics: |
19 | 19 |
|
@@ -52,7 +52,7 @@ UI5 applications face significant challenges when consuming NPM packages: |
52 | 52 |
|
53 | 53 | - **Out-of-the-Box Integration** — NPM packages work without configuration |
54 | 54 | - **Build-Time Transformation** — Automatic bundling during `ui5 build` |
55 | | -- **Dev-Time Support** — On-demand bundling during `ui5 serve` |
| 55 | +- **Dev-Time Support** — On-demand bundling during `ui5 serve` (deferred to [RFC 0017 Incremental Build](https://github.com/UI5/cli/blob/rfc-incremental-build/rfcs/0017-incremental-build.md)) |
56 | 56 | - **Standard Compliance** — Output follows UI5's AMD module format and naming conventions |
57 | 57 | - **Web Component Support** — First-class `@ui5/webcomponents` integration with UI5 control wrappers |
58 | 58 | - **Performance Optimization** — Package independence enables deduplication and browser caching |
@@ -299,7 +299,7 @@ The NPM bundling task integrates into the existing build pipeline as a standard |
299 | 299 |
|
300 | 300 |  |
301 | 301 |
|
302 | | -**Why after `generateBundle`?** The scanner needs all source resources to be resolved and available. **Why before `generateComponentPreload`?** The generated NPM bundles must be included in the Component-preload.js for production deployment. |
| 302 | +**Why after `generateFlexChangesBundle`?** The scanner needs all source resources to be resolved and available. **Why before `generateComponentPreload`?** The generated NPM bundles must be included in the Component-preload.js for production deployment. |
303 | 303 |
|
304 | 304 | #### 3.6.2 Task Interface |
305 | 305 |
|
@@ -697,7 +697,7 @@ Patches are expected to be **temporary**. The recommended lifecycle: |
697 | 697 | - Mitigation: Incremental builds (RFC 0017) will avoid rebundling unchanged packages |
698 | 698 |
|
699 | 699 | 4. **Complexity** — External dependency management requires understanding |
700 | | - - Mitigation: Auto-detection from `peerDependencies` in most cases; clear error messages |
| 700 | + - Mitigation: Auto-detection via transitive dependency consolidation ([Section 3.8.3](#383-externals-discovery-via-transitive-dependency-consolidation)); clear error messages |
701 | 701 |
|
702 | 702 | --- |
703 | 703 |
|
|
0 commit comments