Skip to main content

Module validate

Module validate 

Expand description

Load verification: does this component instantiate against this host?

A plugin built against a drifted or wrong WIT ABI (for example an old configure(config: string) where the host expects a no-arg configure(), or a channel-capabilities flag set the host does not share) will instantiate incompatibly. Today that only surfaces at daemon startup, as a WARN log, after which the plugin is silently skipped — so plugin install reports success for a plugin that will never load.

verify_component_loads closes that gap by running the same type-check and resolved limits the daemon uses at startup, so the failure reaches the operator at the CLI instead of vanishing into a log.

It is the single implementation of that check. plugin install runs it as a gate; plugin info and plugin list --verify run it as a report, for plugins that were installed before the gate existed, installed through --no-verify, or outlived a host upgrade.

Functions§

verify_component_loads
No-backend build: nothing to instantiate against, so verification passes.