Skip to main content
Register the family in your package service provider’s boot() method, after FLEX has registered its services. Supply the built local files that your package ships. Register catalog recommendations through FlexCatalog::registerPlugin() in the same provider-boot phase. Both component collection and catalog registration freeze after providers have booted. A request or queue job cannot add recommendations to the process registry. Catalog services remain lazy on pages that do not use them.
The shared display may be declared last. FLEX checks the complete family before committing its registration. An invalid file, duplicate identity, missing dependency, dependency cycle or asset collision rejects the family without registering its earlier members. Registration supports up to 128 members per family. Use the package generator and asset build to prepare the classes and files.
Use a unique vendor prefix. Extensions cannot replace built-in aliases, shared JavaScript chunks, global styles, registered asset identities or the official FLEX badge.
For a single surface, register($definition, styles: [...], entryPath: ...) uses the same validation.

Continue reading

Extension guides · Definition and registration reference
Last modified on October 17, 2026