Auto-Discovered Components
Component libraries in most platforms require manual registration. Someone on the platform side adds a new component, then updates a list of available components, then that list gets included in a release, and eventually the new component shows up in your builder.
Auto-discovered components skip the manual steps.
Registration Is Automatic
When a new component is added to the platform, it announces its own availability through the platform's component registry. The builder reads the registry at runtime and presents whatever is currently registered.
The moment a new component is available in the platform, it appears in your builder's component library. No action required on your part — no update to install, no feature flag to enable, no configuration to apply.
Metadata Comes With the Component
Each component registers itself along with the metadata the builder needs to present it properly: its name, category, thumbnail or preview, and the configuration options it exposes.
When you select the component in the library, the side panel shows its settings immediately. The component knows what it can be configured to do, and it exposes those settings through the standard configuration interface.
Extensions Add Their Own Components
The auto-discovery mechanism extends to feature extensions. When you enable a shipping extension, the components that extension provides — shipment detail panels, tracking widgets, carrier selection forms — appear in the builder alongside the core components.
Extensions don't require platform updates to make their components available. They register themselves, and the builder discovers them.
Always Current
Auto-discovery means the component library in your builder is always current with what the platform supports. You're not working from a static list that needs to be refreshed — you're looking at a live view of available capabilities.
For platform builders and extension developers, this removes a coordination step from every release. Ship the component; it becomes available. The pipeline from "component exists" to "component usable in builder" is as short as it can possibly be.