Install or manage an extension
Ta treść nie jest jeszcze dostępna w Twoim języku.
Install or manage an extension
Section titled “Install or manage an extension”The Marketplace is the normal place to browse and manage packages and extensions in LM Nexus.
It is not an arbitrary hot-loading plugin system. Packages still go through trust, permission, compatibility, and restart/reload checks.
Marketplace sections
Section titled “Marketplace sections”The side panel contains:
- Browse — package catalog and details;
- Installed / Extensions — built-ins and installed app-data package copies;
- Updates — update and rollback review;
- Sources / Advanced — source trust and export status.
Install a package
Section titled “Install a package”1. Open Browse
Section titled “1. Open Browse”Search or filter the package catalog.
A package card shows status information such as source, compatibility, dependencies, permissions, install state, and whether an update is available.
2. Review Details
Section titled “2. Review Details”Choose Details before installing something unfamiliar.
Pay particular attention to:
- source and trust state;
- compatibility;
- required/optional dependencies;
- requested permissions;
- package/archive checksums where available.
3. Choose Install
Section titled “3. Choose Install”For an installable package, choose Install.
LM Nexus can block the action when required trust, metadata, archive SHA, dependency, compatibility, or duplicate-module checks are not satisfied.
That is expected. Fix the reason shown by Marketplace instead of bypassing the check.
4. Apply the required reload or restart
Section titled “4. Apply the required reload or restart”An installation or profile change may require a frontend reload, backend restart, or generated-app rebuild before it becomes active.
If Marketplace says Module lifecycle action needed, follow the action it shows, such as:
- Reload frontend
- Copy restart command
Manage an installed extension
Section titled “Manage an installed extension”Open Installed / Extensions.
For built-in optional extensions, Marketplace can show Enable / Disable profile controls.
Disabling a built-in module turns it off for the selected profile; it does not delete the module from the application.
Installed app-data packages are managed separately from built-ins.
Update or roll back
Section titled “Update or roll back”Open Updates or use package actions that show Update / Rollback.
Before updating, review changed permissions/trust requirements and the version transition.
Rollback restores an archived package copy when one is available, but activating it can still require the same restart, reload, or rebuild step.
Source trust
Section titled “Source trust”Sources / Advanced separates source enablement from source trust.
Being able to browse metadata from a source does not automatically make that source trusted for package installation.
Expected result
Section titled “Expected result”After any required reload, restart, or rebuild, Marketplace should show the extension in its new state and its UI/features should be available.