adm.js is a simple ~1KB JavaScript library that let's you define bits of code (i.e. modules) which are executed when their requirements are resolved, and then can in turn satisfy other dependents.
It's written in TypeScript for convenience and readability.
Of course.
adm.define('mod1', ['mod2'],
function(mod2) {
console.log("Now me!");
console.log("Thanks for " + mod2)
});
adm.define('mod2', [],
function() {
console.log("Me first!");
return "nothing.";
})adm.js is in design very similar to RequireJS, except it eschews the dynamic loading of modules, only managing when they get executed.
In fact, if you want to bootstrap your javascript as soon as possible, there are some problems with the way RequireJS loads your js. See: script-injected-async-scripts-considered-harmful
The solution to this is to use the <script async> tag, now supported by most browsers. However, you then need to deal with scripts loading out of order. adm.js solves this problem by reordering the execution of your scripts based on their defined dependency tree.
Furthermore, there are other uses for adm.js than just loading scripts. Almost anything can be defined and treated as a requirement for something else. See samples/domReady for an example.
Module packers are great, but they tend to spit out one big 'bundle' of javascript at the end. What if you just need to change a small part of your application? Or update just one third-party library? Your users have to pull down that big 'ol bundle again.
With the age of HTTP/2 coming upon us, it's now more efficient to again break up your code into multiple files that are loaded in parallel via <script async>.
See samples/jQuery for an example of loading a third-party library in an efficient way.
Somewhat. I've made efforts to be compatible with AMD module syntax as long as these modules are defined with an id as the first parameter. This is optional in RequireJS, but now necessary due to the way adm.js is designed.
I've avoided setting the global define function to prevent conflicts with RequireJS, but you can enable this compatibility by uncommenting the code at the bottom of adm.ts.
See samples/jQuery for loading an existing compatible AMD module.
See samples/requireExports for an example of using "exports" and "require" (though the latter is discouraged).
Note that no relative path resolution happens, simply string names are matched to string requirements. Note also that TypeScript's AMD module compiler (annoyingly) doesn't work out of the box because the modules aren't defined with ids.
Simplicity is the ultimate sophistication. So no ;)
Is welcome!