mix mob.plugins (mob_dev v0.7.7)

Copy Markdown View Source

Lists the Mob plugins this project depends on, with tier, hot-push status, and whether each is activated.

mix mob.plugins

A dependency is shown as a plugin if it ships a priv/mob_plugin.exs manifest, or if it is named in config :mob, :plugins in mob.exs. Tier-0 plugins (pure Elixir, no manifest) are indistinguishable from ordinary libraries until activated, so they appear only once listed in config :mob, :plugins.

A manifest whose signature doesn't verify is not loaded (its tier shows as ?); its row says what is wrong with the signature and how to fix it.

Activation is two-step by design (see MOB_PLUGINS.md): adding a plugin to deps makes it installed; adding it to config :mob, :plugins makes it activated — only then are its contributions merged into the build.

Exits non-zero when activated plugins collide (same component atom, native view key, NIF module, ...), naming each plugin's priv/mob_plugin.exs.