Readonly[Called when the module is activated.
Declared requires are provided as Effect services; CapabilityManager and PluginManager
are ambient (Capability.Service, Plugin.Service).
Optionalprops: anyOptional props passed to the module.
The capabilities of the module.
ReadonlyactivationNormalized activation specification — how and when the module activates.
Unique id of the module.
A unit of containment of modular functionality that can be provided to an application. Activation of a module is async allowing for code to split and loaded lazily.
Ordering between modules is expressed through capability dependencies, not registration order: a module declares the capabilities it
providesandrequires, and the plugin manager activates providers before consumers (topological order). Runtime-event modules (activatesOn) activate only when their event fires. Seeplugin-client/src/ClientPlugin.tsfor a worked example.Idiom
org.dxos.app-framework.moduleActivationOrdering applies: sequencing one plugin module's activation before or after another instead-of: assuming module registration order controls activation order uses: ActivationSpec