Concepts
v0.1.16
The concept pages explain how Mishka Installer works underneath: how an event becomes a module that runs its plugins in order, how plugin statuses and dependencies decide what runs, and why the runtime installer loads only compiled packages.
Read them when you want to know why the library behaves the way it does. The pages below show each one with a short summary.
- How events and plugins work How Mishka Installer builds a module for each event, runs plugins in the caller's process, rebuilds chains and handles missing plugin code.
- Plugin statuses and dependencies The five plugin statuses of Mishka Installer, how stopped differs from held, how dependencies hold and release plugins, and how a chain is ordered.
- How the runtime installer works Why Mishka Installer loads only compiled ebin packages, what an install changes, what it stores, how libraries return after a restart and its limits.