AMD and Inject

0.4.x

OLD: This is an old version of documentation. You probably want the most recent version of this document, from the sidebar on the right.

Inject is an AMD compatible framework and supports the following specifications:

basic
anon
funcString
namedWrapped
require
plugins (as of 0.4.1)

This means AMD ready modules can be used straight away with Inject, just like any other system. To define an AMD module, you should use the define function

define('moduleName', [dependencies], function(dependencyOne, dependencyTwo) {});

The define function takes three parts

an optional module name (if not provided, it will be inferred from the file running)
an optional array of dependencies
a factory function or object. If a function, it will be ran once all dependencies are available. If an object, it will be assigned to the module’s export once dependencies have resolved.

Full details on writing AMD compliant modules are available in the AMD Wiki

AMD Plugins (0.4.1)

As of Inject 0.4.1, it’s possible to enable AMD plugin support using the following config:

Inject.useAMDPlugins()

This allows you to use standard AMD Loader Plugins, with the added benefit of localStorage caching for the plugin code. By default, all AMD plugins loaded with Inject are treated as dynamic, and are rerequested on each occurance. This is due to loader plugins not having their own local resource cache.