marionettejs/backbone.marionette — pull request #1900 by jmeas (2014-09-15 04:44:00+00:00)
Title: first work

An example showing how we might implement a UMD-everything approach.

Details:

1. We specify a 'core' file that every module depends on. This loads up the dependencies of Marionette, creates the Marionette object, and loads up helper functions and objects used by most classes
2. We create a wrapper file for each module that loads up the core library, and then any other dependencies.
3. A build system (not shown here) compiles them to individual files somewhere

The benefit of this approach is that it keeps the UMD wrappers out of the source, so it's effectively hidden from us. Also, by putting the helper methods in the core module, we reduce the number of dependencies that each file has; I think the most would be 3, but the majority will have one.

Is this worth pursuing?