Expand description
Extension sources (-e/--extension, installed packages and the distribution share dir,
all resolved by oino_core::extensions::sources — dist.md §5) plus the builtin:<id>
test components (feature faux) and the WasmRuntime construction.
Load order: share-dir packages, then ~/.oino/extensions, then trust-gated
<cwd>/.oino/extensions, then -e; a package with the id of an earlier one replaces it
in place, so a user or -e copy shadows the distribution. --exclude-extension <id>
drops composed packages by id before instantiation (WP-X2). OINO_DIST_EXTENSIONS
overrides the share dir (empty: disabled).
Every CliLoader builds its own WasmRuntime (the cwd is per instance), but the
engine, epoch-ticker thread, compile caches and local-services hub are process-shared
(oino_wasm_host::EngineRegistry, E-ENGINE): the startup path, every ACP session and a
multi-cwd host share one engine and compile each distinct component once per process.
Structs§
- CliLoader
- Loader for share-dir, installed and
-eextensions (builtin:test components). - Loader
Context - Where packages are looked up.
Constants§
- EXTENSION_
LOAD_ FAILURE_ HINT - The extension load failure hint (D13).