Programmatically trigger a lazy chunk load by compound key. Returns true on success. Useful for dev tools that want to "preload" a chunk.
Read-only snapshot of the registry state — for diagnostic tools.
Groups compound keys by chunkId so inspectors can show "X chunks, Y loaded"
plus the keys covered by each.
How many chunks have finished loading. The total is chunks.length.
Attempt to lazy-load the chunk for a given compound key. Returns true if the key was found in the registry and loaded. Deduplicates concurrent loads of the same chunk.
Format: "BaseClassName::Key" (e.g., "BaseResourceComponent::HomeDashboard")
Register a single compound key with the chunk that provides it.
Format: "BaseClassName::Key" (e.g., "BaseResourceComponent::HomeDashboard")
The chunk descriptor (stable id + dynamic import)
Register multiple compound keys at once (from the generated LAZY_FEATURE_CONFIG).
Wires this registry to ClassFactory as a lazy loader.
After calling this, any ClassFactory.GetRegistrationAsync() or CreateInstanceAsync()
that fails to find a registration synchronously will call back into this registry
with the compound key (baseClassName::key) to trigger lazy loading.
Registry that maps compound keys (BaseClassName::Key) to the chunk that provides them.
Wired to ClassFactory via
WireToClassFactory()so that anyGetRegistrationAsync()orCreateInstanceAsync()call that misses synchronously will automatically trigger the correct lazy chunk load. This replaces the previous pattern where individual components (ResourceContainerComponent, TabContainerComponent, etc.) each had their own retry logic.