title: Any way to use goog.require in development with convention-over-configuration?
body: <p>Is there any way I can use Google Closure <code>goog.require</code> to manage JS dependencies, without having to register each namespace explicitly in a dependencies.js file?</p>
  
  <p>I like the idea of the compiler for production, but for development, I'd like some kind of convention-over-configuration translation of namespace to JS folder/path such that something like <code>goog.require('myapp.module')</code> automatically imports <code>myapp/module.js</code> in development mode (if not already imported), while in production it all gets compiled into a single file.</p>
  
  <p>I seem to remember old versions of <code>dojo.require</code> worked this way. Any idea if Google Closure can do the same thing?</p>