Ticket #2386 (closed defect: fixed)
Provide additional rollup files in addition to dojo.js
| Reported by: | jburke | Owned by: | jburke |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BuildSystem | Version: | 0.4.1 |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by alex) (diff)
Allow the build system to generate multiple roll up files that contain a set of modules, in addition to dojo.js. The other rollup files should not include modules that are in dojo.js.
The work for this was started in a previous commit (forget which one), but was not fully fleshed out.
Some complications:
- How to dynamically load these rollup files? Allow mapping the modules in the rollup file via djConfig.modulePaths (could be verbose) or create the rollup module with a specific resource name (like dojo.rollup1), and have the application change their code to use dojo.require("rollup1") instead of the other requires? That goes against the idea of the build system where you don't need to modify your code (except top level djConfig/dojo.js script line). So favor configuration via djConfig.modulePaths.
- Need to divine the correct subset of modules that should be in dojo.js. For instance if rollup1.js has a dependency on dojo.foo and so does rollup2.js, then we should include dojo.foo in dojo.js even if they don't explicitly mention that module for dojo.js.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.