Originally Construct came with a require config, the reasoning being that it will be tested against specific versions of jQuery, Handlebars, Backbone etc and updated occasionally with stable versions of these libraries
As the libraries get updated independently, already loaded on the client-side or even may be optional (ex. backbone-app), to avoid conflicts in (re)setting the require config it is best if the library is decoupled from the require config and allow the dependencies to be broadcast in a less intrusive way.
Originally Construct came with a require config, the reasoning being that it will be tested against specific versions of jQuery, Handlebars, Backbone etc and updated occasionally with stable versions of these libraries
As the libraries get updated independently, already loaded on the client-side or even may be optional (ex. backbone-app), to avoid conflicts in (re)setting the require config it is best if the library is decoupled from the require config and allow the dependencies to be broadcast in a less intrusive way.