Diagnose plugin registration

Start with the global status query after the configurator becomes ready:

const api = await window.iConfigurator.ready()

console.table(api.getPluginStatus())
console.table(api.getSnapshot().pluginErrors)

Inspect one plugin by its stable ID:

const registration = window.iConfigurator.getPluginStatus('customer.dealer-recommendation')
console.log(registration)

Registration statuses

Status	Meaning
queued	Discovered but not yet registered.
registered	Accepted by the plugin system.
setting-up	The setup callback is currently running.
ready	Setup and applicable lifecycle callbacks completed.
failed	A setup or lifecycle phase failed.
disabled	The descriptor was retained for diagnostics but not enabled.
disposed	The plugin was unregistered and cleaned up.

Failed registrations include a public error and errorPhase when available. Timestamps identify when discovery, setup, readiness, failure, and disposal occurred.

Inspect the configurator snapshot

const snapshot = window.iConfigurator.getSnapshot()

console.log(snapshot.status)
console.table(snapshot.plugins)
console.table(snapshot.pluginAssets)
console.table(snapshot.pluginErrors)

pluginAssets reports whether external plugin files loaded successfully. A file can fail before registering a plugin, so inspect both asset and registration status.

Enable development diagnostics

Set this before the embed script on a test page:

<script>
  window.IconMediaConfig = {
    debugPlugins: true,
  }
</script>

Do not enable verbose diagnostics solely to compensate for missing plugin error handling.