0.4.0: Debug by default

Prior to 0.4.0, rave did not work well with browsers debuggers. Break points didn't always work. In certain cases, whole files wouldn't display at all.

In 0.4+ you can debug node, AMD, and global scripts as easily as <script> tags!

These debugger problems were caused by browser bugs, not rave. However, we replaced the eval-based module evaluation techniques with script injection techniques which eliminated all of the known issues.

Furthermore, debugging is now always on for rave, itself. Debugging is turned on for rave extensions by default, too, but can be turned off via bower.json or package.json configuration. See the docs for more info.

As part of this refactor, debug-related code has been separated. This allowed us to fine-tune the production-related modules to be much faster and leaner. For instance, production code will still use faster, leaner eval-based module evaluation techniques instead of slow, bulky script injection techniques.