modulejs.run

[dmgr]

modulejs.run

[lrsjng]

@dmgr just use modulejs.require() for that..

[dmgr]

It doesn't work, because if you have this order of code snippets:

  modulejs.require('lib_a', function(lib_a) {
    console.log('using lib_a');
  });

  modulejs.define('lib_a', function() {
    console.log('lib_a loaded');
    return {};
  });

You will have a:
Uncaught Error: [modulejs-32] id not defined "lib_a"

The hypothetical "modulejs.run" function might work thanks to observers working in "modulejs.define" function and when that observer will recognize that all libraries are defined to run particular code snippet defined by "modulejs.run" method, it will fire it.
Of course "module.require" can work like that so then "modulejs.run" wouldn't be necessary.

[lrsjng]

That will not work at all, as require expects a single id argument only, no callback.

I think the best way to run your code is after all js is loaded, for example:

document.addEventListener('DOMContentLoaded', function () {

    var app = modulejs.require('main');
    app.start();
});

or with jQuery:

jQuery(function () {

    var app = modulejs.require('main');
    app.start();
});

but I understand your request now..

[dmgr]

Yes, I thought about that solution and I think it will be done using that workaround.
Anyway, something like:

    modulejs.require(['lib_a', 'lib_b'], function(lib_a, lib_b) {
        lib_a.start();
    })

or/and:

    modulejs.require(['lib_a', 'lib_b'], function() {
        var lib_a = modulejs.require('lib_a');
        lib_a.start();
    })

in addition to:

    var lib_a = modulejs.require('lib_a');
    lib_a.start();

would be cool ;)