title: Angular add modules after angular.bootstrap
body: <p>I'm using meteor + angular. My intention is to add more dependencies after the app bootstrap (This is because the package is the one handling the bootstrapping at the start and I don't have much control of it). Now while doing that, I would also want to enforce a basic code structure wherein for example, I would compile all controllers in one module.</p>
  
  <p>Here's the basic idea:</p>
  
  <pre><code>'use strict';
  
  angular.module('app.controllers', [])
  
      .controller('MainCtrl', function() {
          // ...
      })
  
      .controller('SubCtrl', function() {
          // ...
      })
  
      .controller('AnotherCtrl', function() {
          // ...
      });
  </code></pre>
  
  <p>Then include that to the main module as dependency:</p>
  
  <pre><code>angular.module('app', [
      'app.filters',
      'app.services',
      'app.directives',
      'app.controllers' // Here
  ]);
  </code></pre>
  
  <p>After some research, I've discovered that what I'm trying to do (Adding dependencies after bootstrap) is actually a part of a feature request to the angular team. So my option is using, for example,  <code>$controllerProvider</code> and <code>register()</code> function:</p>
  
  <pre><code>Meteor.config(function($controllerProvider) {
      $controllerProvider.register('MainCtrl', function($scope) {
          // ...
      });
  });
  
  Meteor.config(function($controllerProvider) {
      $controllerProvider.register('SubCtrl', function($scope) {
          // ...
      });
  });
  
  Meteor.config(function($controllerProvider) {
      $controllerProvider.register('AnotherCtrl', function($scope) {
          // ...
      });
  });
  </code></pre>
  
  <p>It's works though not that elegant. The questions are:</p>
  
  <ul>
  <li>What's a more elegant way of doing the <code>config</code> and <code>register</code> part?</li>
  <li>Is there a way to register a module instead?</li>
  </ul>