Hi Alex, thank you for your response.
I looked at most of those references and actually used the custom download builder when creating my build, but my issue still exists. I have each individual kendo module, but many of them include code for the same AMD components. For instance, "barcode" includes "util/main", and so does "grid." If I have both of those components on the page at the same time, that means I have to load the exact same code for "util/main" twice, even though it's only needed once. My question was more focused on separating out those internal dependencies (the "util/main", "mixins/observers", etc), and including a dependency to the appropriate internal dependency in each kendo module.
To illustrate this example, for the barcode file, there are 4 AMD defined code blocks. "util/main", "util/text-metrics" (which requires "util/main"), "util/base64" (which requires "util/main"), "mixin/observers", and the actual module "kendo.dataviz.barcode" (which only requires "kendo.dataviz.core" and "kendo.drawing"). Instead of this approach, could there be separate files for the different internal dependencies, then have "kendo.dataviz.barcode" depend on "kendo.dataviz.core", "kendo.drawing", util/main", "util/text-metrics", "util/base64", and "mixin/observers" (or have util and mixin modules which contain all of the specific modules like main, text-metrics, and base64 for util).
I haven't tried the gulp distribution because it looks like it will yield the same results as the custom download, but if there is a way to reconfigure the gulp approach to achieve those results that could work.