Name of the module
List of modules which the injector will load before the current module
OptionalconfigFn:
ModuleConfigFn
Register an options-backed application host custom element.
The definition is installed when the module runs. The host element is a native custom element backed by an AngularTS child scope.
Custom element tag name.
App component options.
The $controller service is used by Angular to create new controllers. This provider allows controller registration via the register method.
Controller name
Controller constructor fn (optionally decorated with DI annotations in the array notation)
Register a named reactive mode machine as an injectable service.
The machine is created by $machine when the
named service is requested. The returned instance is not
tied to any one scope lifetime; it registers with
AngularTS scope proxies when assigned to a controller or
scope.
Register a REST resource as an injectable service.
The resource factory is delegated to the
$rest provider, keeping REST support
configurable by custom runtimes.
Service name.
Base URL or URI template.
OptionalentityClass:
EntityClass<T>
Optional constructor for mapping JSON.
Optionaloptions:
RestOptions
= {}
Optional RestService options.
Register a pre-configured SSE connection as an injectable service.
The connection is created by $sse when the
named service is requested.
Injectable name.
SSE endpoint.
Optionalconfig:
SseConfig
= {}
SSE connection options.
Register a router state during module configuration.
This is equivalent to calling
$stateProvider.state(...) in a config
block, but keeps route declarations in the same fluent
module API used for components, services, directives,
and custom elements.
State declaration with a name.
Register a named router state during module configuration.
The provided name is copied onto the state
declaration before it is passed to
$stateProvider.
State name.
State declaration without a required
name.
Register a persistent object store as an injectable service.
Store construction is delegated to
$provide.store, which creates the service
through the injector and persists it through the
selected backend.
Service name.
Constructor, factory, or object to persist.
Storage backend type.
OptionalbackendOrConfig:
StorageLike
&
PersistentStoreConfig
Custom backend or persistence options.
Allows undefined
Register a named WebAssembly module as an injectable service.
The actual loading is delegated to the
$wasm provider, so custom runtimes can
decide whether WebAssembly support is included.
Injectable name used to access the module exports.
URL of the .wasm file to fetch and
instantiate.
Optionalimports:
WebAssembly.Imports
= {}
WebAssembly import object.
Optionalopts:
WasmOptions
= {}
WebAssembly provider options.
Supported keys:
boolean
false (default): the injectable
resolves to instance.exports.
true: the injectable resolves
to
{ instance, exports, module }.
Register a user-authored native custom element backed by an AngularTS scope.
The element class must extend ScopeElement.
Its static template, shadow, scope, inputs, and isolate
properties configure the AngularTS wiring.
Custom element tag name.
Custom element class.
Register a pre-configured WebSocket connection as an injectable service.
The connection is created by
$websocket when the named service is
requested.
Injectable name.
WebSocket endpoint.
Optionalprotocols:
string[]
= []
Optional subprotocols.
Optionalconfig:
WebSocketConfig
= {}
WebSocket connection options.
Register a pre-configured WebTransport connection as an injectable service.
The connection is created by
$webTransport when the named service is
requested.
Injectable name.
WebTransport endpoint.
Optionalconfig:
WebTransportConfig
= {}
WebTransport connection options.
Register a named Web Worker connection as an injectable service.
The actual connection is delegated to the
$worker provider, so worker support remains
provider-driven instead of directive-driven.
Injectable name.
Worker script URL.
Optionalconfig:
WorkerConfig
= {}
Worker connection options.
Register a named workflow as an injectable service.
The workflow is created by $workflow when
the named service is requested. Workflow behavior
remains local to its WorkflowConfig; the
provider does not apply global workflow defaults.
Modules are collections of application configuration information for components: controllers, directives, filters, etc. They provide recipes for the injector to do the actual instantiation. A module itself has no behaviour but only state. A such, it acts as a data structure between the Angular instance and the injector service.