I saw @mixonic mention in his EAK article that he modified it to work with more than one app in the repo. I’m looking for some feedback on the best way to go about having more than one app, and having some shared/common resources that can be optionally imported into each app.
It appears that EAK blindly concatenates all files together, and doesn’t consider the actual import dependencies when deciding what to include in the build. The requirejs optimizer, for example, can combine files based on the actual dependency tree, which seems valuable so that you only build explicit dependencies into your files. That becomes particularly useful when certain modules require a shared resource, instead of the app (index.html) needing to know which shared resources each of the modules need, it will be built in based on the fact that the module imported it.
I’m admittedly new to Ember App Kit, so let me know if what I’m saying doesn’t seem to make sense, or goes against the philosophy. @mixonic, do you have an example of your multi-app EAK repo? Anyone else deal with similar issues?