RequireJS Loading order

commonjs-wrapper.js

// This doesn't appear to be the case...
define(function (require) { 
	
	// Is there any guarantee that `moduleA` is loaded first?
	var loadMeFirst = require('moduleA');
	var loadMeSecond = require('moduleB');
	
});

standard-require.js

// In this case `moduleA` *appears* to always be loaded before `moduleB`
define([ 'moduleA', 'moduleB' ], function (loadMeFirst, loadMeSecond) { 
	
});

There is no guarantee of load order with either approach. All scripts are loaded async and only guarantee is that the factory functions above are not called until both dependencies have been loaded and evaluated.

Thanks for clarifying that, James. I ended up with this approach which seems to do the job - could you confirm it's the 'correct' way to handle ordered dependencies?

// Application main entry point definition.  Load any configuration options which relate to the framework actors
// before loading the frameworks themselves.
define(['logger-config', 'jquery-mobile-config'], function () {

    // Logger and jQueryMobile configs have been loaded, now for the app...
    require(['songbook/app', 'jquery-mobile'], function(app) {

        // jQuery-Mobile and app are ready to go!
        app.init();
    }); 
});

If you are using requirejs 2.0, the shim config is helpful for this kind of situation where you have implicit dependencies (the library does not call define()) but want to use it as a module:

http://requirejs.org/docs/api.html#config-shim