Dependencies
Overview
The Dependencies section in the file explorer provides a dedicated area for managing external libraries and packages that have been added to the project. Dependencies are maintained separately from the project's source files and are versioned alongside them within the Version Control System. This separation ensures a clear distinction between the project's own code and the third-party packages it relies on.
Dependencies are displayed under the Dependencies root node in the file tree. Each dependency appears as an entry in the tree with its name and version information.
Adding Dependencies
To add a new dependency, right-click on the Dependencies root node in the file tree and select Add Dependency from the context menu. This opens the dependency library browser, which provides access to the platform's package registry. The registry can be searched by package name, and available versions are listed for each package.
After selecting a package and version, the dependency is added to the project and appears in the Dependencies section of the file tree. The addition is recorded as a transaction in the Version Control System.
INFO
The platform's package registry synchronizes every 24 hours. Newly published packages may not be available in the registry for up to 24 hours after publication.
Managing Dependencies
Existing dependencies can be managed through the context menu. Right-clicking on a dependency entry provides the following actions:
- Edit - Modify the dependency's configuration or version.
- Rename - Change the display name of the dependency.
- Delete - Remove the dependency from the project.
All dependency management operations are recorded as transactions in the Version Control System, providing a full audit trail of dependency changes.
Dependency Installation
When a project is built or deployed, dependencies are automatically installed on the target device in an isolated virtual environment. This isolation ensures that project dependencies do not interfere with the device's system packages or with dependencies of other projects running on the same device.
WARNING
After adding, updating, or removing a dependency, a new build and deployment is required for the changes to take effect on the target device. Dependency changes in the file explorer are not applied to running programs until the project is redeployed.
